3 ms·
That's what Dart was supposed to be, in Google's eyes. The problem is both that it needs buy-in from all browser vendors (and the webdev community), and more im
by Vinnl 9y ago
That's what Dart was supposed to be, in Google's eyes. The problem is both that it needs buy-in from all browser vendors (and the webdev community), and more importantly, that you'll now need to support both Javascript and the new language indefinitely. Especially considering that new mistakes will be made with the new language, and new quirks introduced, that doesn't sound that attractive.
- hajile 9y agoGoogle gave up on dart as an browser language quite a while ago. It now sees use server-side and in flutter (a native UI layer).
- Vinnl 9y agoYeah, I said that's what it _was_ supposed to be ;)
- tym0 9y agoMy understanding is that they use it for most of their front-end work but compile it to javascript. See angular-dart.
- hajile 9y agoYou are completely correct. I was considering that to be like ocaml, kotlin, scala, etc which transpile to JS. For what it's worth, I think either ocaml or SML is far better than dart for compiling to JS, but dart is far better than typescript (and has a more sound type system). It's not a huge wonder that Google apparently uses angular-dart instead of the typescript version.