Hopefully not in the same way that Dart turned out to be so "exciting and interesting" :)
Hopefully not in the same way that Dart turned out to be so "exciting and interesting" :)
Perhaps a question of expectations: "The big question is whether Google originally intended Dart to replace JavaScript".
https://insights.dice.com/2019/03/27/fall-rise-dart-google-j...
Dart 1.0 Optional Types runtime checks
Dart 2.0 Mandatory Types (sound null-safe type system) static checks + runtime checks.
All the key designer from Dart 1.0 left Google shortly after Chrome dropped support.
The language only got rescue thanks to AdWords not wanting to rewrite their stack yet again (they had recently migrated away from GWT).
Afterwards Flutter provided the necessary funding to keep improving the language as they replaced JavaScript with Dart.
Language evolution is an interesting thing, especially when you've got corporate influence, second system effect etc. Or simply the need to add stuff, as languages are considered just another product, and otherwise you're considered "stale" in today's market. Weird.
They’ve all left now (I don’t know what Lars’ involvement is anymore?).
But I was curious about Dart for a cross platform app and learned Dart 2.0 and was wholeheartedly let down. I just felt like I was staring at a Java dialect. The “sanctioned” tutorial I watched introduced classes as a “way of organizing code” which I guess could abstractly be said to be true, but IMO misses the mark entirely.
Anyway, I found Dart 2.0 to be very uninteresting. Very safe and traditional and boring. Maybe I need to relook closer to try and see what you’re seeing that I did not.
because…?
for example…?