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].
Comments
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