OneLang

I started to write a comparison page here, but missing a lot of important aspects: https://github.com/koczkatamas/onelang/wiki/OneLang-vs.-Haxe... Tl;dr: you cannot use One in production now, but the grand plan is to make One as hackable and flexible as I can. So here is the plan: - the compiler does not contain any target language-specific part, you can add a new language by creating a few hundred lines of template file (this actually works already, it is not just a plan) - rewrite One in One, so you can convert from any language to any language in any language - there is no StdLib, but libraries can be created by anyone. We publish interface and implementation definition separately, and you can eg. implement a Web client interface for PHP and Node, while somebody else can implement it for C# and Swift. Behaviour defined by interface tes

I realize it's sometimes not considered cool to point out competing projects, but the OneLang project FAQ explicitly says that it's a proof of concept, not ready for production use, with no documentation, and may never be finished. https://github.com/koczkatamas/onelang/wiki/FAQ OneLang does seem like a nifty project, but given its current state, it seems pretty reasonable to point toward Haxe for anyone interested in something similar that has been around for years, well documented, and used in production by many teams.

From https://github.com/koczkatamas/onelang/wiki/FAQ it is clear that this tool falls far short of actual polyglottery.