This makes a lot of sense from a teaching perspective. If you're introducing programming to Korean-speaking kids, having keywords in their own language removes one abstraction layer. They can focus on the logic without also needing to memorize what 'while' or 'return' means in English first.
Curious about persistence - does this support RDB/AOF snapshots or is it purely in-memory? That's usually the first question that comes up when teams evaluate Redis alternatives.
The read-only past is a nice touch. I kept abandoning journaling apps because I'd spend more time editing old entries than writing new ones. This removes that trap entirely.
One thing I'd want: the ability to export everything as plain text or markdown. If the app ever goes away, I want my data.
Solo dev, working on a native macOS app in SwiftUI. AI has been most useful for the boilerplate - repetitive view layouts, FileManager calls, figuring out AppKit bridging weirdness. It basically replaced Stack Overflow for me.
Where it breaks down is state management. The suggestions look right but introduce subtle bugs in how data flows between views. I've learned to only use it for isolated, well-scoped tasks. Anything that touches multiple components, I write myself.
