No, not really, it's the same way that C compilers are written in C. The first one was written in another language like assembly, to be sure, but after that you could use the first compiler to write a second compiler in C, and the second one to write a third one, and so on.
In this case, I'm assuming the first version of the compiler was written in Javascript. After that, they could use the first Javascript-based Litescript compiler to compile a Litescript version of the compiler, and once you have that you never have to go back to Javascript again.
Re:Show HN: LiteScript
by basicallydan on Sunday March 09, 2014 @05:05PM
(#7369966)
Cool, I did think it might be that, but when I read "LiteScript is written in LiteScript, every new version must be able to compile itself to be ready for release" it just kinda makes it sound like some kind of magic is happening, where a version of the language, before even being compiled, can somehow compile itself in some super clever way that I was just missing.
Thanks for the explanation :)
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...
That's the result of compiling https://github.com/luciotato/LiteScript/tree/master/devel/so...
Ah. Nice. Thanks. Need to dig down.
It's quite common for compilers to be written in the language they compile.
---
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...