Thanks for you comment! Sorry if it sounded like a click-bait to you. I'm pretty sure that any article like "Language X is better than Y" will be highly opinionated and subjective. If there could be objectively the best language, all other languages would not be needed.

I disagree that singleton should be named an anti-pattern. It's just a construction which cannot be good or bad. It all depends on how and where you use it – and the usage can be either appropriate or not.

Regarding the null safety – yes, I know that it's already in technical preview. Team is working hard to integrate it in Flutter, my point here was rather that it should be done from the very beginning (of course, it's my opinion, and obviously the team had some reasons not to do it).

But I disagree that null safety introduced in Dart is going to be far better than Kotlin's one. Yes, there are other languages on JVM and they can cause you problems when used with Kotlin, but Dart also has interoperability with e.g. JS and C, so the same thing can be said about Dart as well. Moreover, currently you can introduce this null safety in a part of your project, in a non-breaking way, so it automatically causes all these problems like "this type should be non-null, but it turns out to be null".

Yes, the language is evolving, and some features are requested (though it doesn't necessarily means they will be implemented). I've even put links to these feature requests in some of my sections. Some of these features were requested more than 2 years ago and I doubt that we will get them in the near future.