Dart beat TypeScript to existence by a solid year. The web should run on Dart right now but Google fumbled the ball.
Web search was synonymous with Google until they enshittified their product to irrelevancy a few years back. Where once using Bing was unthinkable, several of my coworkers now happily use it.
They then proceeded to fumble the incredible lead they had with AI just a few years ago. At this point, I wouldn't be surprised if they let their Chrome monopoly slip through their fingers as well.
It's ridiculous how Google's BoD hasn't axed everyone in a leadership role at that company given how many gems they've let slip through their fingers.
The web should run on Dart right now but Google fumbled the ball.
It's clear you didn't see the fervor around this around a decade ago [0][1], as it was universally panned as a move that would only strengthen Google's browser monopoly (as if sites started using more Dart, other browsers would have no choice but to add in Dart support). Personally I am very glad that we don't have a built-in Dart compiler in the browser, compile to JS languages are more flexible and now we have an even more robust and even-handed solution in the form of WASM, as now any language can compile to an open standard, not just Dart (which also has WASM support now).
Another argument in favor of not having Dart in Chrome is allowing its development to be much more flexible, as this article shows, rather than being hampered by the standards committee [2].
Whilst I can agree mostly with your last three points I don't think any company, even apple, could at this point replace JavaScript on the web. It's too ingrained. Sure there's typescript but that's not a whole sale replacement, the end result is still JavaScript.
Yeah but you've still got to convince everyone to rewrite all the JavaScript in it. That's a big ask even for Google with a faster VM. If they'd pushed it I would predict chrome market share taking a dive.
Personally I think they did the right thing pivoting away from trying to replace JavaScript.
Comments
Dart beat TypeScript to existence by a solid year. The web should run on Dart right now but Google fumbled the ball.
Web search was synonymous with Google until they enshittified their product to irrelevancy a few years back. Where once using Bing was unthinkable, several of my coworkers now happily use it.
They then proceeded to fumble the incredible lead they had with AI just a few years ago. At this point, I wouldn't be surprised if they let their Chrome monopoly slip through their fingers as well.
It's ridiculous how Google's BoD hasn't axed everyone in a leadership role at that company given how many gems they've let slip through their fingers.
It's clear you didn't see the fervor around this around a decade ago [0][1], as it was universally panned as a move that would only strengthen Google's browser monopoly (as if sites started using more Dart, other browsers would have no choice but to add in Dart support). Personally I am very glad that we don't have a built-in Dart compiler in the browser, compile to JS languages are more flexible and now we have an even more robust and even-handed solution in the form of WASM, as now any language can compile to an open standard, not just Dart (which also has WASM support now).
Another argument in favor of not having Dart in Chrome is allowing its development to be much more flexible, as this article shows, rather than being hampered by the standards committee [2].
[0] https://news.ycombinator.com/item?id=3600874
[1] https://news.ycombinator.com/item?id=9264531
[2] https://news.ycombinator.com/item?id=40355071
Whilst I can agree mostly with your last three points I don't think any company, even apple, could at this point replace JavaScript on the web. It's too ingrained. Sure there's typescript but that's not a whole sale replacement, the end result is still JavaScript.
Dart’s JS VM was reportedly faster than vanilla JS. It could have wholesale replaced JS if Google had really leaned into it.
Yeah but you've still got to convince everyone to rewrite all the JavaScript in it. That's a big ask even for Google with a faster VM. If they'd pushed it I would predict chrome market share taking a dive.
Personally I think they did the right thing pivoting away from trying to replace JavaScript.
Early Dart was a significantly worse language even compared to early Typescript. And remained so for a very long time.
Plus what the sibling comment said about Google monopoly.