Well, for me things like BLoC, ChangeNotifiers, Providers etc. are good, but they are more about connecting your BL and UI. What I need for proper implementing BL is better type system (and I don't say that Kotlin has the best implementation, e.g. TypeScript has some interesting features that Kotlin doesn't), ADTs, and other things I've mentioned in the article.

Yes, you can emulate some of these things with code generation or libraries, but I would prefer to have it built in.

I totally understand that the team is facing some challenges; they're working hard and are doing a great jobs without any doubts. When all the things are implemented I will be more than happy to write another article "Why Dart is not worse than Kotlin", or maybe even "Why Dart is better than Kotlin". Again it will be opinionated article and I don't expect the Kotlin team to start making Dart out of Kotlin.

But we're living now, and for now, Kotlin looks more mature and safe to me, despite the fact that they are more or less of the same age. Whether it is because they lack resources, or because it's "feature not a bug" – for me, as a user, it doesn't matter.

> There is a priority on features that make Flutter more efficient

That's totally understandable. Maybe that's the reason why Flutter is great and Dart is mediocre. For me. For now.

> Also, quite a few of your complaints here are opinion based.

Sure. Again, all the articles "Why language X is better than Y" are subjective and opinionated. I don't claim that my opinion is the only right one. But that's my opinion.