[cyber_kinetist]

Not bad for mobile apps, but still sucks a lot for desktop support.

Also, really wished they've opted for a more general language like C# rather than Dart - but that's inevitable since Google needed to make use of their Dart language after they've failed to standardize it on the Web (and I think they don't want to use a language developed by Microsoft of all companies)

[wiseowise]

They've picked Dart because it was the only language that could have small aot binaries, hot reload capable runtime without compromise and most importantly because they could influence development of the language.

C# is one of the worst choices they could make at the time.

[cyber_kinetist]

Yeah good point. Although C# nowadays has good AOT support, that wasn't the case in the early days of Flutter (Google could have collaborated with Microsoft to develop this, but why would they?...)

[greatgib]

I don't think so, I think that some teams at Google were trying hard to push Dart that no one wanted. And so Flutter was about to create a framework that was supposed to be the main and only one for Android app and co in the future (at that time) to force us on switching to Dart.

[wiseowise]

No.

[mrsmrtss]

Why would C# be the worst choice? Do you gave any real arguments or is it just your biased opinion.

[mrsmrtss]

Sorry, made a typo with 'gave' -> 'have'. But the point stays , why would C# be (one of) the worst choices here (when C# has small AOT binaries, hot reload etc)?

[cyber_kinetist]

Nowadays C# has good AOT support, but it wasn't when Flutter was in its infancy.

[wiseowise]

> when C# has small AOT binaries, hot reload etc

In 2015?