3 ms·
It's sad that Gilad's obsession with Smalltalk led to this. I feel that Dart could have been a more serious competitor in that space if it was fully statically
by incepted 11y ago
It's sad that Gilad's obsession with Smalltalk led to this.
I feel that Dart could have been a more serious competitor in that space if it was fully statically typed. No optional types. This would lead to a more credible language and, obviously, a more performant one.
- munificent 11y agoA number of people on the Dart team are working on strong mode[1], which is very close to what you're asking for. I say "very close" because "No optional types" is ambiguous. Type annotations are still optional in strong mode because in most cases it will infer the static type for you. Strong mode still also supports a dynamic type—much like C# does—because that's useful for things like interop or working with data. Strong mode was initially created because it helps produce cleaner JS (unsurprising that static types help with static transpilation) but what we're hearing from customers is that they like it for better type safety and tooling. Even many of the Flutter[2] folks, who don't compile their Dart code to JS at all, are using strong mode because they get better static checking. [1]: https://github.com/dart-lang/dev_compiler/blob/master/STRONG_MODE.md https://github.com/dart-lang/dev_compiler/blob/master/STRONG... [2]: http://flutter.io/ http://flutter.io/