LiteScript

I've used PEGs to create a compiler, and it results in clear, readable code, easy to maintain. Because the parser structure it's cleaner, it feels natural to write the parser manually with PEGs. The key is to handle parse-fail with exceptions. Instead of having a syntax-file and a generated parser, the code is clear enough to act as low-level documentation. see: https://github.com/luciotato/LiteScript

Litescript is literate from the start. https://github.com/luciotato/LiteScript

pure JavaScript has too many ways to introduce subtle bugs into large projects, which also become a nightmare to maintain. From a hacker perspective, node.js and js are great. js is a beautiful and extremely powerful lang. From a "business" perspective -even more if your business data better fits a RDB-, IMHO, javascript, node.js+ a LARGE business project are a recipe for disaster. (If you add ORM to the mix, you're doomed). http://blog.codinghorror.com/object-relational-mapping-is-th... I believe a compiler-to-js like Typescript makes using JavaScript+node in a large business project more manageable (disclaimer: I've not tried Typescript, but I've coded my own compile-to-js lang out to frustration with medium-to-large js projects: https://github.com/luciotato/LiteScript ) TL;DR: My two cents: Not a good business case for a business IF a

Great questions!, I guess I didn't express myself correctly. I meant: LiteScript is designed with the Grammar https://github.com/luciotato/LiteScript/blob/master/source/G... separated from the "production" of target code https://github.com/luciotato/LiteScript/blob/master/source/P... I "want" to (and think I can) add new "producer" modules other than "producer_js", but I've not even started. The idea -so far- is to compile to a node native extension http://nodejs.org/api/addons.html#addons_hello_world so most C answers are: V8's With respect to PHP, I think it's simpler. The idea is to generate PHP but do not support all PHP quirks, just generate PHP code that is "js-like", (PHP mimics allmost all js functionality) and have support libs in LiteScript unifying APIS. Some things like "eval" can throw a compiler error, when the target is PHP

That's the result of compiling https://github.com/luciotato/LiteScript/tree/master/devel/so...

But this is still in Javascript. I thought the whole point was to produce a LiteScript compiler in LiteScript to compile to LiteScript. https://github.com/luciotato/LiteScript/tree/master/devel/li...

From the GitHub Page [0]: --- Real use cases so far On the server: LiteScript itself LiteScript is written in LiteScript, every new version must be able to compile itself to be ready for release. LiteScript is a real-use case of a heavy, server run, text processing, class based program written in LiteScript. --- I'm must be missing something here, but this kinda blows my mind a little bit. Somewhere in the compilation process there must be somethign which isn't LiteScript? Anyway, this does look cool. Good job. [0]: https://github.com/luciotato/LiteScript#real-use-cases-so-fa...

The compiler is PEG-based, very easy to extend. Check the grammar: https://github.com/luciotato/LiteScript/blob/master/source/G...