Google Chrome: the New Web Platform?

snydeq writes "The Chrome dev team is working toward a vision of Web apps that offers a clean break from traditional websites, writes Fatal Exception's Neil McAllister, in response to Google's new Field Guide for Web Applications. 'When you add it up, it starts to look as though, for all the noise Google makes about Web standards, Chrome is moving further and further apart from competing browsers, just by virtue of its technological advantages. In that sense, maybe Chrome isn't just a Web browser; maybe Chrome itself is the platform — or is becoming one.'"

Re:No meat to this story

[rreyelts]

How can this be +5 insightful with less than 10 comments on the entire post? It turns out that if you do a search for the phrase "a multi-billion dollar web advertising company with a history of privacy violations", you'll discover this is just spam propped up by puppet accounts. Slashdot, you need to clean house.

Re:No meat to this story

[MisterMidi]

It's just the continuation of web 2.0. Like it or not, there IS a distinction between traditional sites and web apps and I think it's a good idea to have some sort of standard or guidelines of how web apps should feel and behave. That's all Google did. The guide talks about using existing and new standards like HTML5, CSS3 and Javascript, being consistent and providing a good user experience. Nowhere does it say anything about Chrome-only or Google-only features. The InfoWorld article is just sensationalism.

Re:Another 'standard' to contend with?

[mspohr]

If you will read the "Field Guide" you will discover that it is all based on HTML5 which is a standard that all browsers should support.

Re:Hello - WebKit? JavaScript?

[salesgeek]

The -webkit stuff is nothing to be shocked by. It's just a step towards eventually becoming part of the css standard. There are tons of -moz properties as well. Take -border-radius, which is now part of the standard. Before it was part of the standard it was -webkit-border-radius and -moz-border-radius. So, the whole -webkit thing is just a step on the trail to standardization.

When you see a company stuck on XP, there is simply not a good reason for it anymore. Most often, being stuck on XP or IE6 means the company IT department is not able to keep up with change and are doing things like it is 1997. They are using a software installation model that is based on physically inserting CDs to perform upgrades and often are unable to cope with distributing a security patch in a timely manner.

It is high time that CEOs realize if their people are using IE6 or WinXP, that the CIO and CTO should be sacked. Sorry, but there is no excuse for keeping your company stuck in the 1990s. Also, if you develop web apps, the right move is always to discontinue support for IE6. If you are feeding the monster, you are part of the problem.

Re:No meat to this story

[evilviper]

Those figures are about customers staying with the same phone manufacturer, NOT THE PLATFORM. With iOS, you only have one manufacturer, with Android, there's dozens. So Android could be at 25% as people switch back and forth between Motorola/HTC/Samsung/LG and yet not have a single customer switching away from Android.