3 ms·

If you look at great science projects like the LHC, a lot of the funding is "wasted" building the infrastructure needed to actually build the project, while Moz

If you look at great science projects like the LHC, a lot of the funding is "wasted" building the infrastructure needed to actually build the project, while Mozilla missed the target a few times "Firefox OS", I never saw Rust with bad eyes, it was made to enable Firefox to become a top tier browser again.

tmzt 9y ago
It's like CERN, why did they waste all those resources on this World Wide Web thing? Couldn't they just linotype their papers like everyone else?
Brakenshire 9y ago
Ironically Firefox OS would become a lot more viable with these sorts of performance improvements. Using Firefox Nightly I have actually felt an occasional sensation of blurring between native and web, because of how quickly some sites render and respond. I wonder how applicable these innovations will be on the mobile web. You'd have thought parallel processing would be particularly important in mobile processors where the single core speed is often a fraction of the multi core speed.
- dralley 9y ago
  Firefox OS was ahead of it's time in the most literal sense. What they really should have done was FIRST work on all these new web APIs that allow you to make web apps that can accomplish things that only native apps could do before. They didn't exist 5 years ago, and that was a problem. Perhaps if they focused on making web apps as capable as native apps first, it would have been a viable platform.
  - Manishearth 9y ago
    All the PWA stuff Chrome is doing is basically moving in this direction, from the opposite end, really. Instead of building an OS that needs a web based app system, they go in reverse by taking their existing OS and allowing for webapps to be work more like regular apps. This probably will involve more APIs and such.
  - kevingadd 9y ago
    Building new Web APIs was a core pillar of Firefox OS development, and it applied to desktop Firefox as well. Unfortunately these efforts were bogged down by poor executive leadership and the difficulty of getting any other browser vendor to take new APIs seriously, so the work went pretty slowly. Gamepad API spec efforts began as part of this, for example. Then another vendor kicked their own inferior spec out the door without talking to anyone and that ended up being the de-facto standard (not the first time). Other APIs like exposing battery status, network connectivity status, and the ability to notify with vibration were in the works, just to name a few I remember.

tmzt 9y ago

It's like CERN, why did they waste all those resources on this World Wide Web thing? Couldn't they just linotype their papers like everyone else?

Brakenshire 9y ago

Ironically Firefox OS would become a lot more viable with these sorts of performance improvements. Using Firefox Nightly I have actually felt an occasional sensation of blurring between native and web, because of how quickly some sites render and respond. I wonder how applicable these innovations will be on the mobile web. You'd have thought parallel processing would be particularly important in mobile processors where the single core speed is often a fraction of the multi core speed.

dralley 9y ago
Firefox OS was ahead of it's time in the most literal sense. What they really should have done was FIRST work on all these new web APIs that allow you to make web apps that can accomplish things that only native apps could do before. They didn't exist 5 years ago, and that was a problem. Perhaps if they focused on making web apps as capable as native apps first, it would have been a viable platform.
- Manishearth 9y ago
  All the PWA stuff Chrome is doing is basically moving in this direction, from the opposite end, really. Instead of building an OS that needs a web based app system, they go in reverse by taking their existing OS and allowing for webapps to be work more like regular apps. This probably will involve more APIs and such.
- kevingadd 9y ago
  Building new Web APIs was a core pillar of Firefox OS development, and it applied to desktop Firefox as well. Unfortunately these efforts were bogged down by poor executive leadership and the difficulty of getting any other browser vendor to take new APIs seriously, so the work went pretty slowly. Gamepad API spec efforts began as part of this, for example. Then another vendor kicked their own inferior spec out the door without talking to anyone and that ended up being the de-facto standard (not the first time). Other APIs like exposing battery status, network connectivity status, and the ability to notify with vibration were in the works, just to name a few I remember.