Post a Comment
Good question. I am very sceptic, too. Also, Android's success is quite a problem for Chrome OS, IMHO. The OEMs are just getting familiar with Android right now, the flood of upcomming devices is right around the corner and consumers seem to like Android quite a bit with it's more traditional general purpose approach.
If you mean the animation where the phone writes "HTC quietly brilliant" on the screen... yes. The animation has really nothing particular, it's rather mediocre.
Hopefully, something will be actually happening behind the scenes. Each time I wonder what could be so time-consuming in a stupid phone's boot process.
Well, it's easy to explain. Consider that DOS took around 30s to boot the hardware of the old days, and Windows 7 and Mac OS X still take about the same time on hardware that's thousands of time faster.
How is that possible ? Software bloat. At each new releases, the devs of modern operating systems aim for that 30s mark, arguing that if people don't complain about it enough it's just good enough. Good enough by good enough, they save a lot of development time in optimization, and it just works as long as hardware processing power is growing according to Moore's law...
Now, what happens when some manufacturer releases a new product based on old hardware, like a smartphone or a netbook, and tries to stick a desktop OS on top of it ? On that slower hardware, the wasted power hurts performance more than expected by the OS manufacturer. And we get 45s to 1min boot times, among other things like crappy battery life. Blame the hardware manufacturer for not putting a core i7 and a 4400 mAH/12.7V battery in the device.
The more I work on my OS, the more I'm horrified by how unnoticeable the performance impact of basic features now is. I'm growing more and more convinced that it's superfluous features that no one uses that are so much harming performance.
In fairness, modern boot sequences are doing a lot of useful work that DOS never did. For example, DOS just pulled the Centronics RESET pin low across all 3 printer ports (whether they existed or not ;-) for a few seconds and called the peripherals good, then stuck up a default mode 0 text screen with a prompt. Not that challenging, but then, with only 160k and a 4.77 MHz processor...
A modern OS walks the entire USB tree, validating and loading drivers dynamically as it goes, brings up one or more networks, dynamically configures video for the current set of monitors, loads a boatload of desktop extensions and configuration settings... It's not just "bloat", it's very useful work given a billion users with very different preferences, hardware and peripheral sets.
Of course, focusing effort on boot time (by moving some configuration into the background, for example) can result in much faster boot times. For example, the last two Ubuntu releases together cut my desktop boot times by a factor of three.
That said, I reboot my devices (phone to server) so rarely I don't particularly care. It's more of a first impression consideration - "wow, Ubuntu boots fast!" - than a real productivity boost.
A modern OS walks the entire USB tree, validating and loading drivers dynamically as it goes, brings up one or more networks, dynamically configures video for the current set of monitors, loads a boatload of desktop extensions and configuration settings... It's not just "bloat", it's very useful work given a billion users with very different preferences, hardware and peripheral sets.
Of course, focusing effort on boot time (by moving some configuration into the background, for example) can result in much faster boot times. For example, the last two Ubuntu releases together cut my desktop boot times by a factor of three.
That said, I reboot my devices (phone to server) so rarely I don't particularly care. It's more of a first impression consideration - "wow, Ubuntu boots fast!" - than a real productivity boost.
Yes, they do more, but I don't think it's enough.
With modern hardware, generating an identity-mapped page table for 2 GB of RAM is done in a very small fraction of second, and I'm suspicious that it's the same with probing PCI and USB since the OS is more or less polling high-speed peripherals through an uncluttered bus.
Adaptation to multiple hardware and user configurations can slow down the thing a lot, yes, but only at first boot. At later boot, if there's no change in system configuration, I think the OS can just go full speed as if it was made for the user's specific configuration.
But I need more coding work before I can back this claim with experimental data.
Edited 2010-10-14 16:35 UTC
ChromeOS (or ChromiumOS) runs very well on the original eeePC 700-series, much better than any full-blown Linux install does. It's allowed us to bring our eeePC 701s up-to-date in terms of web experience.




