Leviathan

This isn't just a hypothetical, either. This was the problem I ran into with the Clojure IDE that I was writing[1]. I had to drop down to C to write the lexer/parser and to store the AST. Because of this design decision, traversing, searching, and manipulating this AST was much less pleasant and more error-prone than it was in the initial Objective-C prototype. This is where Julia will shine for me. It will let me "drop down" to more efficient mechanisms when I need to write efficient algorithms, allowing me to use the same tools at all levels. This is actually my new plan for my IDE, I hope to embed Julia in it and rewrite most of the app in Julia. This should also make it dead-simple to let users extend the app by scripting it in Julia, while still having first-class access to the same internal ASTs used by the app itself. [1]: https://

I wrote a Clojure IDE[1] in Objective-C with a good chunk of it (parser/lexer) written in C. But I gave up on the effort, because of difficulties integrating a scripting language with C, and because writing in C is kind of annoying. At this point, the project is probably dead. It's currently only barely useful. Should I take it down, or leave it up? I could see one argument for taking it down being that it might confuse people who are looking for a real IDE and find it somewhat-broken instead. On the other hand, one argument for leaving it up could be that someone else might take it over. And maybe there are more things I'm not taking into account. Hence I come to you for advice. [1]: https://github.com/sdegutis/leviathan