Linked by Thom Holwerda on Sat 7th Dec 2013 00:55 UTC
Microsoft

"It's pretty much a brick," says Pawn Stars' Rick Harrison as he rejects a Samsung Chromebook brought in by an actor playing a customer. Microsoft really doesn't want you buying this thing.

But why? Just how big of a threat are Chromebooks, Google's oft-ridiculed web-only laptops, to Microsoft's core business?

I'm puzzled too. It doesn't seem like Chromebooks are that big of a threat - why create terrible advertisements that only provide Google with free publicity?

Permalink for comment 578171
To read all comments associated with this story, please click here.
RE: Comment by Flatland_Spider
by galvanash on Sat 7th Dec 2013 07:05 UTC in reply to "Comment by Flatland_Spider"
galvanash
Member since:
2006-01-25

Google has successfully turned Chrome into a runtime environment and created an app ecosystem that is platform independent. Once people are using Chrome apps the obvious conclusion is to get rid of OS X or Windows and use an operating system dedicated to running Chrome.


No offense but I think you are giving Google a little too much credit... Yes, Google is certainly the poster child for packaged web apps, and the first browser vendor to put a real marketing push behind them (i.e. Chrome Apps) - but Google isn't the only cook in the kitchen.

http://www.w3.org/2012/sysapps/
http://www.w3.org/2000/09/dbwg/details?group=58119&public=1

There is a fairly diverse group of people working on this, Mozilla, Intel, Samsung, Adobe, etc. Its not just a Chrome thing, although at this point in time Chrome has the most complete implementation. Quite a bit of the foundation of what constitutes a "Chrome Apps" was designed and built by Mozilla...

Chrome was a great play, and Google has done a good job of looking where the others weren't while hiding its hand. Mozilla had an inkling of this with Prism, but that was more about being a code base to build applications off of. Google Gears was a first tentative attempt at creating offline web applications, but it was always limited by being an add on.


Prism and Gears (and also WebOS) were not dead ends - those are the technologies that got Google from there to here... And I don't think Google has been hiding their hand at all - they are very open about their goals.

Chrome is about being everything to the application. Everyone else was looking at the web browser as being a portal to web apps running on servers, and Google was looking at erasing the line between the two by making Chrome a runtime environment.


Again, I think you have a very Google centric view of this... All the major browser vendors are trying to do this - and they are mostly working together to do it. Google is certainly a bit ahead and have built up the most infrastructure for exploiting it for their own use - but its not a "Google" thing.

...What is FirefoxOS? There are of course differences between it and ChromeOS, but not many. From the point of view of a developer, most of the differences boil down to hardware specific stuff (FirefoxOS is primarily about phones, ChromeOS is primarily about laptops). They both run what are essentially packaged apps, and their apis are more similar than different (and rapidly converging).

Just saying, Its not Google vs everyone else.

Reply Parent Score: 7