3 ms·

I'm not sure about asm.js/OdinMonkey. I believe that FirefoxOS 1.0 does not have it, but that FirefoxOS 1.1 (which should be available as a free over-the-air up

by Yoric 13y ago

I'm not sure about asm.js/OdinMonkey. I believe that FirefoxOS 1.0 does not have it, but that FirefoxOS 1.1 (which should be available as a free over-the-air update) has it. More generally, FirefoxOS does not automatically get the latest version of Gecko, because the process for mobile operating systems is more complex. The operating system must first pass certification by (if I recall) both the constructors and the operators. This operation is both long and costly, so it is probably impossible to follow the Firefox desktop/Android 6 week release cycle for the time being. However, if I had to guess, I would assume that FirefoxOS will receive about one big update every few months, with all the new features and optimizations of Gecko. I know, for instance, that some of the optimizations I have added recently to Gecko have missed the release train for the next version of FirefoxOS (I believe that's still 1.1) but should be part of the release after that.

mcintyre1994 13y ago
Can you give an idea of how you expect that to work compared with Android? Given that Firefox OS devices seem to be cheap and low end, how likely are constructors and operators to perform a "long and costly" process to upgrade them regularly? Cheap and low end Android devices have terrible support from both, even for upgrades without new hardware requirements, is there any indication that they will better support similar Firefox OS devices?
- deleted 13y ago
  [deleted]
- shardling 13y ago
  I believe that in a previous thread, FirefoxOS devs were hopeful that the way the OS is "layered" will make this less painful -- that upgrading Gecko should be much easier than upgrading Android versions, because it wouldn't introduce driver issues etc. Updating the underlying kernel would be more arduous.
fzzzy 13y ago
1.1 is still the b2g18 branch, so no asm.js. 1.2 will be the version that pulls from master (gecko 26 I think?) and will have asm.js.
- Yoric 13y ago
  Oh, it's 26? In that case, they have not missed my recent I/O optimizations :)

by Yoric 13y ago

mcintyre1994 13y ago

Can you give an idea of how you expect that to work compared with Android? Given that Firefox OS devices seem to be cheap and low end, how likely are constructors and operators to perform a "long and costly" process to upgrade them regularly? Cheap and low end Android devices have terrible support from both, even for upgrades without new hardware requirements, is there any indication that they will better support similar Firefox OS devices?

deleted 13y ago
[deleted]
shardling 13y ago
I believe that in a previous thread, FirefoxOS devs were hopeful that the way the OS is "layered" will make this less painful -- that upgrading Gecko should be much easier than upgrading Android versions, because it wouldn't introduce driver issues etc. Updating the underlying kernel would be more arduous.

fzzzy 13y ago

1.1 is still the b2g18 branch, so no asm.js. 1.2 will be the version that pulls from master (gecko 26 I think?) and will have asm.js.

Yoric 13y ago
Oh, it's 26? In that case, they have not missed my recent I/O optimizations :)