Chrome

Sep 04, 2008 13:01

Google's latest squeeze in the slow strangulation of Microsoft is something that's been on my software wishlist ever since the catchphrase "Web 2.0" started getting thrown around: a browser architecture that's designed on the principle that web apps really are individual apps and should be treated accordingly by the hardware, rather than having one ( Read more... )

techne

Leave a comment

(I like parenthesis) steveniles September 4 2008, 21:40:42 UTC
I don't think Chrome is so much about getting a new browser into the mix (IE, FF, Safari, Opera, Konqueror, etc) of which there are many (too many if you're a web developer (However I think it uses the same render agent as Safari)). I think it's about getting new browser ideas into the mix. If Google had come out and said "We should all rethink some of the assumptions we make about browsers and the web" people would say "Yeah!" and go back to what they were doing (This probably has already happened, I forget...). But Google puts out a whole new shiny browser, it gets talked about (and here we are ( ... )

Reply

Re: (I like parenthesis) steveniles September 4 2008, 21:41:31 UTC
(Needless to say, I not only downloaded it the moment it was released, but also listened to the press conference live while at work)

Reply

Re: (I like parenthesis) steveniles September 4 2008, 22:32:53 UTC
Re: (I like parenthesis) ihuitl September 4 2008, 23:32:29 UTC
Good comic. It's my perspective on alot of computing in general.

Reply

Re: (I like parenthesis) steveniles September 5 2008, 02:39:10 UTC
/agree
I find there's often times when my response can be stated in the form of xkcd hotlinks

Reply

Re: (I like parenthesis) nyuanshin September 5 2008, 04:25:27 UTC
Argh, thanks for spotting the thread/process gaffe. My geek neurons are getting rusty.

I think you're on the money -- they're pushing for convergence on good ideas that'll help their business model in the long run, and that was the best way to do it. Aside from just being good ideas in themselves, the ground-up stuff was to get the attention of programmers, and the aesthetic choices are geared toward making the users forget that they're running the browser in an OS. In both cases there's the subtle but powerful suggestion of "hey look guys, doesn't this huge expensive layer running under the browser seem superfluous?" Or maybe I'm reading too much in.

Reply


Leave a comment

Up