Linked by Thom Holwerda on Thu 19th Nov 2009 20:01 UTC
Google Google has just unveiled its Chrome OS operating system during a press event at the company's headquarters, and it's pretty much exactly what we expected it to be: a streamlined Linux kernel booting straight into the Chrome web browser. The code is available starting today.
Thread beginning with comment 395485
To read all comments associated with this story, please click here.
What I expected and Litl is dead.
by kragil on Thu 19th Nov 2009 21:14 UTC
kragil
Member since:
2006-01-04

It is mostly what I expected. Moblin + Chrome

So no new windowing system. Plain old X11 is the windowing system (pimpled with OpenGL, Clutter etc.)

Things I like: Firmware, Security model, Open Drivers (I really hope they put pressure on the hardware vendors, that would give them A LOT of creds with the FOSS crowd.)

But I think they have to provide Native Client apps really fast .. people want native speed.

And btw. Litl is dead. ChromeOS seems to do the same (but more thoroughly executed) and will be "Less than free"(like Android)

Reply Score: 3

galvanash Member since:
2006-01-25

It is mostly what I expected. Moblin + Chrome

So no new windowing system. Plain old X11 is the windowing system (pimpled with OpenGL, Clutter etc.)


No new windowing system... yet.

But I think they have to provide Native Client apps really fast .. people want native speed.


You might be right. I don't _know_ anymore that you do, but I really don't think that is going to happen. I think Google is going to intentionally a permanently avoid a native API for the following reason:

As long as the only thing Chrome OS runs is web apps, they can change virtually anything in it as they see fit - and as long as they can get Chrome (the browser) to run on it they maintain their ABI (essentially the browser itself IS their ABI). Without having to worry about maintaining binary compatibility with anything, they can effectively optimize the living sh*t out of it over time so that they can reduce their hardware requirements over time (or increase performance on existing hardware depending on how you look at it).

I think the whole point is to make the hardware itself as uninteresting as possible - Chrome OS is for running cloud apps, and running them as cheaply as possible.

So sure, it is little more than moblin + chrome NOW, but as long as they avoid getting trapped by having to support native apps, they can work on shrinking their OS stack. I predict X will be the first thing to go...

Reply Parent Score: 2

vivainio Member since:
2008-12-26

So sure, it is little more than moblin + chrome NOW, but as long as they avoid getting trapped by having to support native apps, they can work on shrinking their OS stack. I predict X will be the first thing to go...


Having Native Client does not imply that they would commit to native app support. It just means you can run native code in the browser sandbox, for performance. Binary browser plugins as such are not sandboxed right now.

Reply Parent Score: 2

pepa Member since:
2005-07-08

Open Drivers? I am actually somewhat worried about the OEM validation policies (although I guess they can be hacked out). I will put pressure on selected hardware vendors, but I'd call it partnerships.
Then, no hard-drives is another funny one... The vision if for light(weight) machines, that store as little as possible locally. I guess this can also be easily hacked around. But will the firmware be modifiable as to allow for a different kernel, with all the checksumming?

Reply Parent Score: 2