Linked by Thom Holwerda on Tue 24th Nov 2009 17:28 UTC, submitted by waid0004
Permalink for comment 396175
To read all comments associated with this story, please click here.
To read all comments associated with this story, please click here.
News
Linked by Thom Holwerda on 05/18/13 21:06 UTC
Linked by Thom Holwerda on 05/18/13 7:37 UTC
Linked by fran on 05/18/13 1:38 UTC
Linked by Thom Holwerda on 05/17/13 23:35 UTC, submitted by kragil
Linked by MOS6510 on 05/17/13 22:22 UTC
Linked by Thom Holwerda on 05/17/13 22:15 UTC, submitted by Tom
Linked by Thom Holwerda on 05/16/13 21:41 UTC
Linked by Thom Holwerda on 05/16/13 17:04 UTC
Linked by Thom Holwerda on 05/16/13 13:17 UTC
Linked by Thom Holwerda on 05/16/13 12:06 UTC
More News »
Sponsored Links



Member since:
2006-01-25
Google has no business interest in conventional OS development. Chrome OS is an engine for running a browser. Ive pointed this out before, and it doesn't seem to be a very popular opinion, but all Google wants in the end is a shim to but a browser on top of some hardware - the OS is the shim, and that is all it needs to be.
The fact that it has started out as essentially equivalent to a full Linux distribution is just for convenience to get the ball rolling. It won't be long before it gets whittled down to the bare minimum needed to run Chrome and thats about it. The point is that Google's goals do not at all coincide with Haiku's or even the goals of Linux for that matter - they are only interested in the OS to the point of enabling them to run their browser on as little hardware as possible.
Thats not to say they couldn't for instance use Haiku (instead of Linux) as their "OS" for running Chrome. Hell, that might even be a good idea. But would the Haiku project benefit much from that? To put it bluntly, their notion of security is to make the OS a black box that the user cannot alter - that isn't of much use if you actual intend to let users run anything native on it...