3 ms·

That's not what he's actually saying there; that's a list of technical bullet points, not market adoption. However, even if we talk about market adoption; how

That's not what he's actually saying there; that's a list of technical bullet points, not market adoption. However, even if we talk about market adoption; how is Firefox OS holding up against iOS, Android, and Windows? > What part of that statement is incorrect? "Always bet on JS" from Brendan Eich really meant, for 16 years, starting in 1998 and during the time that Firefox was most influential over the future of the web: "I'm never going to bet on anything other than JS". It's a uselessly self-fulfilling declaration when its stated by a (now former) browser vendor executive.

pcwalton 11y ago
> That's not what he's actually saying there; that's a list of technical bullet points, not market adoption. 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. > However, even if we talk about market adoption; how is Firefox OS holding up against iOS, Android, and Windows? 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.
- 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 ago
      That'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?

pcwalton 11y ago

> That's not what he's actually saying there; that's a list of technical bullet points, not market adoption. 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. > However, even if we talk about market adoption; how is Firefox OS holding up against iOS, Android, and Windows? 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.

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 ago
    That'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?