The main problem with Firefox OS was that it was really slow. At the same time it was targeting budget phones.
But on the other hand progress was quite good. Back in the days I was maintaining unofficial images for Alcatel Fire. Each version was a little bit faster, but you really can't do much when the whole OS is a browser running on a device with with 256MB of RAM and a single core CPU.
Wasn't webOS effectively an OS built on web standards and effectively just a browser engine?
The Pre had 256MB and something like a 600mHZ processor. While it was no speed demon, I was always impressed with the animations and multitasking they pulled off with it.
That one order of magnitude is about 7 years behind the Moore's Law. We're still progressing but it's slower, more expensive and we hit way more walls than before.
Switch 2 seems to be more up to standard. I was able to charge it with a normal phone charger and also the Switch 2 charger seems to work with everything else unlike the one for Switch 1. Fortunately I never bricked anything with that, but it just never worked with anything other than the console.
Switch 1 require the charger to support pd2 12v to charge at all. Some changer may decide to skip that voltage, and support only 9v and 15v. So Switch is not happy about it.
Every device in my room except for switch supports more than one voltage config. Wondering why on the earth switch decided to handle voltage setting like this.
Usually, pd charger will label their supported voltage config. And you can read that label to find out whether a charger will work with switch or not.
Source: I do use my phone charger to charge switch during traveling
Also notice, some charger will disable part of the supported voltages when there are more than one device connected. Mine apparently drops 12v when there are other device connected (thus prevented switch 1 from charging)
The author used kernel compilation as a benchmark. Which is weird, because for most projects a build process isn't as scalable as that (especially in the node.js ecosystem), even less after a full build.
These constants are defined mostly to make serialization of infinite/NaN values simpler and more obvious, but can be used to indicate a "largest possible value", since an infinite value gets clamped to the allowed range. It’s rare for this to be reasonable, but when it is, using infinity is clearer in its intent than just putting an enormous number in one’s stylesheet.
But on the other hand progress was quite good. Back in the days I was maintaining unofficial images for Alcatel Fire. Each version was a little bit faster, but you really can't do much when the whole OS is a browser running on a device with with 256MB of RAM and a single core CPU.
reply