2 ms·
Bootstrapping your compiler is a vanity project for languages. It's cool to show you can do it, but pretty pointless in a practical sense unless your language i
by ModernMech 9y ago
Bootstrapping your compiler is a vanity project for languages. It's cool to show you can do it, but pretty pointless in a practical sense unless your language is targeted at building compilers.
- pjmlp 9y agoIt is not vanity at all. It takes out of the table the typical argument that the language is not serious enough because it is written in C or something. The usual old time joke "my compiler compiles your language".
- ModernMech 9y agoNot all languages target C or C like workloads. Not all languages are particularly good at expressing parsers either. If your language is targeting e.g. Writing graphical visualizations, I don't see how writing compilers in the language serves anyone's interests except the language designer's.
- pjmlp 9y agoI agree if the language is something very specific like SQL, or an extension language to embedded as plugins. Otherwise any general purpose language, should be able to be used for all kinds of application, including compilers.
- cjhanks 9y agoAdditionally, writing a compiler really helps a team find their edge cases much faster. Without a major software undertaking for an immature language, most of those bugs would be found (and likely not reported) by users. But yeah, there's a little vanity too.
- ModernMech 9y agoSure writing a compiler can help there, but like I said, there are probably better ways to test that taking into account the design goals of the language. If you find that writing compilers is a pain in your language, but no one in your community is using your language to write compilers, are you going to invest resources in making your language better at writing compilers, or are you going to work on things important to your community?
- cjhanks 9y agoYeah, that's a good point. In the sense, RubyOnRails was a great blessing to the language.