In addition, it has complicated a lot of stuff for a long time due to build setups, bugs related to toolchains around Dart and Angular 2's repository, lengthier CI runtimes, and more. It was a huge net negative for those looking to contribute, even for simple changes.
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.
> having to write code a certain way because of dart sucks
> having to write code a certain way (because of dart) > sucks