Thanks for your comment!

No, it's not like comparing oranges and apples, it's like comparing programming language and programming language :)

I know that there were reasons to choose Dart for Flutter and I'm not saying "you should re-write all the Flutter into Kotlin". These are just my thoughts about why I like Kotlin better than Dart.

I totally agree that instead of Kotlin I could put any other language. But in my everyday life I work with Kotlin and Dart, so these are languages that I know better that others. And in my opinion some features in Kotlin are made better than in Dart – that's what I'm writing about. Actually, comparing Dart with Kotlin makes sense to me, since their use cases and backgrounds are pretty similar: they are both relatively young (the projects started in 2010-2011); they both are claimed to be multi-purposed and suitable for BE, FE, scripts, mobile (and both are most popular in mobile development); they both have interoperability with JS and C; they both can be compiled and interpreted; both companies developing the language have their vision of "cross-platform framework". And yet Kotlin looks much more mature and strict to me.

Again, I'm not saying that Google should abandon Dart and use Kotlin instead (though, as for me, that would be awesome). I'm saying that some things in Dart should be done differently. And I'm definitely not alone in this opinion: there are links to feature requests in my article that are saying the same. Unfortunately, some of these feature requests are more than 2 years old and there's little chance of getting them any time soon.