71–80 of 180 posts
Earlier quoted context omitted.
The barrier to replacing X is not replacing X, it is the significant rewriting of software that uses X.
And the first massive hump there is getting the replacement good enough to even bother thinking about rewrites. Google has a chance to leap past that, because they've contrived a situation where they not only don't need X, they don't need to port X apps.
If ARM and x86 are targeted, this means no Flash (not surprising, given how poorly it runs on Linux), which presumably means YouTube will be operating in full-on HTML 5 video mode by the time these devices launch. If netbooks continue their meteoric ascent, and if Chrome OS grabs a significant share of the market, we may finally see the realization of the mythical Year of Linux On the Desktop. The ironic aspect, of c…
I get the impression they are trying to repackage their cloud services together: it would make sense if the plan for Chrome OS is to ultimately tie it all together.
I wonder just how Google Native Client will fit into this, especially extended with things like USB support and OpenGL. There's games, obviously, but what about a NaCL port of iTunes? It's not that far-fetched.
I think we can expect very close integration of Native Client into the Chrome OS as soon as or right after it goes public. To the level of accessing hardware ports to control external devices right from your Native Client web-app.
Imagine drivers that get loaded and updated on-the-fly. Of course, Google will have to implement a smart security mechanism (along the lines of RSA authentication for dynamic device/driver coupling) and provide a way for device manufacturers to register their driver's public keys with Chrome OS.
Key Data Point: > The software architecture is simple — Google Chrome running within a new windowing system on top of a Linux kernel.
I wonder if people will be able to take this new windowing system and use it for their own purposes. That would be fantastic, if the new windowing system is good.
I believe both Qt and GTK+ can be compiled to draw directly to the Linux framebuffer, if you don't want to use X (although they don't exactly provide much in the way of window management).
If ARM and x86 are targeted, this means no Flash (not surprising, given how poorly it runs on Linux), which presumably means YouTube will be operating in full-on HTML 5 video mode by the time these devices launch. If netbooks continue their meteoric ascent, and if Chrome OS grabs a significant share of the market, we may finally see the realization of the mythical Year of Linux On the Desktop. The ironic aspect, of c…
If ARM and x86 are targeted, this means no Flash (not surprising, given how poorly it runs on Linux), which presumably means YouTube will be operating in full-on HTML 5 video mode by the time these devices launch. If netbooks continue their meteoric ascent, and if Chrome OS grabs a significant share of the market, we may finally see the realization of the mythical Year of Linux On the Desktop. The ironic aspect, of c…
Whether Google wants or needs it is another question.
Let's hope this also means that a Linux version of Chrome is around the corner.
Chrome wasn't built in a day. Though you'd think if they're announcing a linux-based operating system, centered on their web-browser, making their web-browser run on linux would be trivial. OTOH, could it be the diversity of linux distributions that's making it difficult for them?