I have nothing to add to the arguments I've made for why I think turning Nim into a platform that's not monogamously married for life to a single language frontend would broaden Nim's appeal.
I would just like to express my utmost respect for all people who've weighed in on this discussion, even if you disagree. It is entirely possible that I am wrong. The final decision is of course up to Araq / core dev team. Furthermore, special plugable frontend support inside the Nim compiler itself isn't necessary to make the Nim ecosystem a fountainhead of alternative language design. Nim's powerful metaprogramming features already make it a great platform for basic [DSL](https://en.wikipedia.org/wiki/Domain-specific_language) development. More complex [LOP](https://en.wikipedia.org/wiki/Language-oriented_programming) approaches can be simplified via richer syntax parsing libraries written in Nim, for writing compilers in Nim that take arbitrary higher-level syntax and compile it to Nim code (while also exporting Nim's libraries to the new language), and the standard Nim compiler would take over from there.
