I built this because I was totally new to writing parsers, and I liked Instaparse but wanted a faster feedback cycle. I was also excited to use CodeMirror with ClojureScript, two of my favorite tools. More broadly, I'm interested in the future of browser-based coding - I think there's a bright future in small, problem-specific coding environments in which the language, editor, and UX are carefully mapped to a particular problem.
Just as Excel is primarily graphical but allows power users to write formulas, with CodeMirror and Instaparse one can imagine designing a small language and mini-editor to expose advanced functionality within an app. (Here I expose options as an editable Clojure map instead of with a GUI.)
h34t|10 years ago
I built this because I was totally new to writing parsers, and I liked Instaparse but wanted a faster feedback cycle. I was also excited to use CodeMirror with ClojureScript, two of my favorite tools. More broadly, I'm interested in the future of browser-based coding - I think there's a bright future in small, problem-specific coding environments in which the language, editor, and UX are carefully mapped to a particular problem.
Just as Excel is primarily graphical but allows power users to write formulas, with CodeMirror and Instaparse one can imagine designing a small language and mini-editor to expose advanced functionality within an app. (Here I expose options as an editable Clojure map instead of with a GUI.)