This is the Google Chrome OS netbook keyboard -- Engadget

If you really believe there's no use case for ChromeOS I think you're interacting with a very small subset of people.

I'll be the first to admit it probably isn't appropriate for power users. But most users aren't power users and those people are plagued with level upon level of complexity and bugs that inhibit their work.

I'm in charge of an IT department and the 5 most common complaints are all related to issues the Chrome OS should, in theory, fix. And that's just business users.

Think about home users who have to deal with virus scanners, malware, adware, errant programs running in the background, system updates and so on. Not to mention the simple cost advantage (Even academically priced Office still costs $100 in itself).

Finally Microsoft hasn't maintained Windows as well as it should have. So you have a shell that's been around since 1993 that is constantly getting new stuff tacked on to it. If you deal with it for long enough you start to see these flaws very clearly. Things like Wireless connections failing for no good reason (which are fixed with a simple right click and repair) or explorer grinding to a halt simply because the user tried to access a resource that wasn't there.

So there's plenty of use case here. Whether Google executes well enough is another story but there's definitely a need.

I feel the same way. Except I don't hope I am wrong. Just the first part.

To me all power buttons should have a delay hold on them (ie you have to hold it for 2 or 3 seconds), then placement doesn't really matter. I can't even count how many times I have turned off my laptop via the docking station while plugging a usb cable into it.