Yes, after programming ever since I was 15, I've learned that it has to be one of both: _ Either I have to accept the basic design choices made in a piece of code as is, and build upon it in the same line of thought - Or, if I really don't want to live with that, I start out completely fresh, not even looking at existing code, since it will just distract me from my path In this case I opted for the second approach. Many transpiler projects out there are somehow related. As you can see by the source code Transcrypt isn't. I needed a fresh approach to reach my goals (the shopping list in the docs). People ask: why not add this or that to an existing project. Answer: because it isn't that simple. For me multiple projects existing alongside each other isn't a problem, but a fact of nature. There exist many C/C++ compilers, prog languages, OS'es, processor chips. Diversity and survival of a rich, diverse set of fit-enough creatures is what drives IT as well, in my view.

Exactly. There are currently is also brython.

Stop reinventing the wheel everytime something you want is missing from a lib. Try to contribute to said lib first.

Otherwise, this adds noise, wastes ressources and splits point of focus in the FOSS community.

I understand the appeal of writting your own baby, I understand the ego part too.

But remember this is a projet you then have to maintain and document. People will ask about their problems with it on stackoverflow, they will type "X vs Y vs Z" on Google.

Creting a new project has consequences.

Yes it currently works and is systematically tested on Windows and Linux. OSX is planned too. Btw RapydScript also works on Windows, you'll need NodeJS to run it.