[munificent]

> I said having to write the code a certain way when contributing due to Dart support

It sucks in both directions. If you're trying to fix things for Dart users, it's also a real hassle to have to figure out how to back-translate that into some kind of TypeScript that will then be compiled back into the Dart code you have in mind.

Having a single source of truth that you translate to JS/TS and Dart makes a lot of sense when the value you get from sharing outweighs the cost of dealing with the pipeline. My impression is that that cost/benefit hasn't worked out well for Angular. I think being split will enable both sides to move faster, even if it means manually migrating some fixes between the two languages.