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?

Thread beginning with comment 578158
To read all comments associated with this story, please click here.
Comment by Flatland_Spider
by Flatland_Spider on Sat 7th Dec 2013 02:38 UTC
Flatland_Spider
Member since:
2006-09-01

Chrome is the gateway drug and Chromebooks are the full on addiction.

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.

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. 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.

Now that I think about it, this is very similar to what Palm did with the OS on the Pre. It would be interesting to know how much inspiration came from Palm, or if Google was already working independent of Palm.

Reply Score: 7

RE: Comment by Flatland_Spider
by WorknMan on Sat 7th Dec 2013 02:43 in reply to "Comment by Flatland_Spider"
WorknMan Member since:
2005-11-13

Google has successfully turned Chrome into a runtime environment and created an app ecosystem that is platform independent.


Except that it is not platform independent, since it depends on Chrome. Is there even a version of Chrome on Windows Phone? Or Blackberry? Or FirefoxOS?

Reply Parent Score: 2

TechGeek Member since:
2006-01-14

I think he means hardware platform. Chrome comes on ARM and Intel x86. Windows RT is tanking where as Chrome is doing better. And since Chrome is free, you can have a lower cost system. It also requires a hell of a lot less horsepower than Windows 8 for the x86.

Reply Parent Score: 6

galvanash Member since:
2006-01-25

"Google has successfully turned Chrome into a runtime environment and created an app ecosystem that is platform independent.


Except that it is not platform independent, since it depends on Chrome. Is there even a version of Chrome on Windows Phone? Or Blackberry? Or FirefoxOS?
"

Yeah... in the sense you are talking about Chrome Apps aren't platform independent - because those platforms don't run Chrome. But that is because the platforms Chrome doesn't run on (iOS and Windows Phone) actively block any efforts to port to them. I guarantee you if Microsoft and Apple didn't explicitly ban 3rd party browser engines on their platforms Chrome would already be ported to them*... Im leaving out FirefoxOS because it is essentially already capable of running the same apps as Chrome with only minors changes - and the APIs are rapidly converging.

As for Blackberry... They died, didn't you hear ;)

Anyway, Microsoft and Apple don't even have to support porting Chrome to their platforms - they just have to support the rapidly solidifying W3C standards underlying packaged web apps (in their own browsers) and they could run them as well. They choose not to...

The point though is the platform is (or at least will be real soon) W3C standards - not Chrome. Chrome is just an implementation of the runtime for packaged apps - its not the implementation.

* footnote - I don't count Chrome for iOS as a real port of Chrome, as it is nothing more than a thin veneer around the system provided UIWebView. Its not really a browser so much as an alternate skin for Safari.

Edited 2013-12-07 07:27 UTC

Reply Parent Score: 11

Lennie Member since:
2007-09-22

Most of what runs in Chrome is the same that runs on pretty much every modern webbrowser.

Reply Parent Score: 3

modmans2ndcoming Member since:
2005-11-09

that is like bitching about Win32 or Cocoa not being platform indipendant

Reply Parent Score: 2

crhylove Member since:
2010-04-10

LOL @ Windows Phone. How do you even count that? BWAH HA HA HA!!!

Reply Parent Score: -1

RawMustard Member since:
2005-10-10

Good post. It's the same reason the destroyed Netscape!

Reply Parent Score: 3

Lennie Member since:
2007-09-22

Maybe it is just as simple as that:

"Microsoft appears to be wary of the Chrome OS' threat to Office and their apps, a threat that could undermine one of Redmond’s most important revenue streams."

Reply Parent Score: 3

RE: Comment by Flatland_Spider
by galvanash on Sat 7th Dec 2013 07:05 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