3 ms·
1.8 already? Wow. Yet enums are only now being added (the proposal was from 2013) This puts me off Dart - for now - for two reasons. Firstly, the language a
by notjackma 12y ago
1.8 already? Wow. Yet enums are only now being added (the proposal was from 2013)
This puts me off Dart - for now - for two reasons.
Firstly, the language appears to have been rushed. Yes, great tooling, but was the language rushed out the door by corporate Google? Will they ditch Dart just as quickly if it doesn't gain traction? Lots of risk in learning Dart.
Second, if it wasn't rushed out the door, then the language designers made a mistake. It's nice they can admit that but it also shows a lack of conviction and belief in the language they have created. So what makes Dart unique? If I want Java, I use Java. Contrast with Golang and the reasons the team give for not having generics.
- tosh 12y agoFrom what I see Dart was definitely not rushed. On the contrary. The team puts a lot of thought into what goes into the language and what doesn't (from a language, implementation and tooling pov). With languages it is easy to add stuff but hard (often impossible) to remove it so it is important to understand the change and make sure it fits well with what is in the language and what might be added later. It obviously helps to have a great team that has done exactly that many times over for many many other languages used in production. Dart is a very clean language and I guess it made sense to postpone non-essential stuff like Enums & Async/Await. This doesn't mean those aren't awesome and great to have, it just means those things like other things better aren't rushed into the language but well thought through.
- oblique63 12y agoDart only looks like java (this was a deliberate design choice to increase familiarity and ease learning/adoption), but it works a lot more like ruby and go.