Slashdot Mirror
Google Releases Source To Chromium OS
Kelson writes "Google has released the source to what will eventually become Chrome OS, and will begin developing it as an open source project like Chromium. The OS differs from the usual computing model by (1) making all apps web apps (2) sandboxing everything and (3) removing anything unnecessary, to focus on speed." Reader Barence adds "Google said consumers won't be able to download the operating system — it will only be available on hardware that meets Google's specifications. Hard disks are banned, for instance, while Google said it will also specify factors such as screen sizes and display resolutions. Google said it plans to officially launch Chrome OS by the end of next year."
This is the infamous network appliance made real. The OS is a simplified kernel with a specific set of supported hardware with a simple interface and no on-system storage for data. All apps and settings are "in the cloud" i.e., on google's servers.
For likely 90% of home users, this will be perfect. A relatively dumb device that only runs a web browser to use web apps (googles or anyone else's provided their signed by google) to do their work.
It takes user-friendly to an extreme and makes everything just part of the web browser experience.
The root OS partition is read only and the selection of hardware is prescribed by google. You can download the source to hack it, but you can't make an installable image as you can't cryptographically sign it for their okay. They're only planning this to be a bought with hardware purchase.
Sound familiar? It should, it's basically the Apple experience made into a net appliance.
I plan to move our company to a "dumb terminal" model over the next couple of years. You say that the cost of hardware just gets "shifted", but this is not entirely accurate. I have roughly 60 users. Each machine must be spec'd to handle the biggest workload, even if that only gets hit during some small fraction of the day. For 99%+ of the day, I have a powerful machine doing very little. With a centralized model, I can smooth that out.
But that isn't the biggest reason I am going to this model. I have folks who can be working in our central office, satellite office, on the road, or at home. I need ways to give my workforce the flexibility they need to work anywhere.
From a cost standpoint, PCs are awful. Maintenance is generally more than the hardware costs. Software installation and configuration alone costs us about 1/4 of a FTE. By centralizing, I am expecting that number to drop by 2/3.
Now, granted, my network is either local, or connected by dedicated T-1's except for our road folks. So, while I think this is a great idea for my workplace, I don't think it makes a lot of sense for me at home.
See my journal for slashdot ID's by year. Mine created in 2005. http://slashdot.org/journal/289875/slashdot-ids-by-year
Really, what does an OS need to do? It needs to manage the network, talk to devices and launch applications. That's it, isn't it? By specifying "no hard disk" Google is cutting out a major part of the device chat. Displaying a folder hierarchy is essentially a search, format and display application. They're good at that.
A large part of the Windows code is managing a large variety of devices, from displays to USB devices. If Google specifies the display format, then there's another large chunk of code dropped. The UI is an application, pointing devices are - devices.
Add an IP stack for the network and stick a security layer in somewhere, if you still need it.
By limiting configuration choices to those that have a broad appeal a *huge* amount of OS can simply go away. You have less local IO, less device chat, and no local disk latency to worry about.
People know how long their network takes to react, and will accommodate that. In contrast, a very thin OS will be very quick and will compare very favourably to a thick OS in response. And if most of the IO is server-side in the cloud, you won't see a lot of IO delays (source of most hangs) and response should be smoother overall, because servers tend to have the best IO controllers and enough spindles to stripe (not that Google would resort to actual hard drives!) Where's the beef?
Do not mock my vision of impractical footwear
Price. No HDD and the ability to streamline components because it only does certain things cuts cost, which in turn cuts price. I can see people buying a "Web Tablet" that they already know all they intend to do with it is just what ChromeOS does, and then they have a normal computer for the real work. It's actually closer to the original "idea" of a netbook. A simple, inexpensive booklet that just does the internet.
Here's a cookie... *psst* it's MAGIC
Because I like not having to configure each mail client on each computer I use, having my entire mail history available to me through a browser, and not having to worry about backing my mail up. The notion of a local mail client is quaint.
Here's something that should be a real concern for geeks. Right now, the ordinary desktop users who don't really need a powerful computer are buying computers. This means that due to economies of scale, the cost of computers is relatively cheap. Imagine what will happen to the price of "powerful desktop-ish machines with full-featured OSes" if 90% of the computing market suddenly starts using these toys. Start preparing to go back to the days of $15,000 computers. Just saying. :-)
Check out my sci-fi/humor trilogy at PatriotsBooks.