3 ms·
> The point is that if JS couldn't do these things, it would be eclipsed by a competitor. It instead grew the ability to do those things, and its competitors ne
by teacup50 11y ago
> The point is that if JS couldn't do these things, it would be eclipsed by a competitor. It instead grew the ability to do those things, and its competitors never gained widespread adoption.
REALLY?? JS can't do concurrency by any objective performance measure against systems providing shared state concurrency; how is a competitor going to eclipse it when the lowest-level syscall interface available to target is JavaScript?
> In terms of languages on the Web, JavaScript has always won. It's clear at this point that the Web isn't going anywhere, even though mobile apps are important.
It ought to be indicative of something that the web is faltering in market segments where programming languages do more than move DOM elements around.
- pcwalton 11y ago> REALLY?? JS can't do concurrency by any objective performance measure against systems providing shared state concurrency https://blog.mozilla.org/javascript/2015/02/26/the-path-to-parallel-javascript/ https://blog.mozilla.org/javascript/2015/02/26/the-path-to-p...
- 14paninta 11y agoThat's a blog post on an experimental approach from 2015. Where is the competitor that could replace JS because JS didn't support concurrency over the past 15 years while the entire world adopted and leveraged SMP and multi-core hardware?