3 ms·
> Dart was originally designed for the client-side as a challenger to Javascript, and I consider it to have generally succeeded in its ulterior goal of spurring
by aikah 11y ago
> Dart was originally designed for the client-side as a challenger to Javascript, and I consider it to have generally succeeded in its ulterior goal of spurring the Javascript standardization committee into greater velocity out of threat of competition
Dart was never a threat to JS in anyway. I don't think it had any effect on ES spec. ES spec evolved "faster" because the committee changed, the old guard (anti OO ) moved on and Microsoft didn't sabotage the effort this time. Things were way different back in 2007 for those who remember it. MS had a commercial interest in not wanting ES4 to succeed ( Silverlight ) while ironically Adobe and the Flash team were pushing for a strong standard. So I fail to see how Dart has anything to do with ES6 success.
- kibwen 11y agoI tend to agree that Dart was never a "threat" to Javascript (smarter hackers than I have remarked at how difficult it would be to have both V8 and the Dart VM playing nicely together), but at the time of its announcement Dart (nee Dash) was certainly the cause of much consternation over potential fragmentation of the web. I recall more than a few of Brendan Eich's impassioned denouncements of Dart during that time. Dart's origin was just as much political as it was technical (though I do think it's transcended that origin to become quite a nice language, though still trying to find its foothold in the dev community).