Main menu:


Add to Google Add to My Yahoo! Subscribe with Bloglines
Check out my GigaDial staton!!


The Public Thinks This Is My Best Stuff

Site search

Hello everyone, my name is John Wall and this is where I write about Marketing and whatever else I find interesting (your mileage may vary). You can also listen to Marketing Over Coffee, a podcast I do with Christopher Penn. I was also involved in the late, great M Show. BTW, I don't look this good, I have a great photographer. I can be reached at: john at themshow dot com

Check LinkedIn for my professional background.

www.flickr.com
This is a Flickr badge showing public photos from jwol3. Make your own badge here.

Categories

Archive

« | Home | »

Why do we need this?

Another browser? Google announces their browser: Chrome

This comic tells the story and here’s what I’m thinking so far.

“Wouldn’t it be great to start from scratch”

Uh. No. Web designers and marketers have taken years to get things to work on 2 platforms, nobody wants a third. You could consider Vista an attempt at starting from scratch, that’s gone well.

P5 and 6 – Multi-threaded browser that’s less of a memory hog – Ok, so I’m a little interested.

P11 – They talk about QA, yeah that’s not a revolution.

P12 – Uses Webkit just like Android. Give me your best Spock… “Fascinating”

P22 – Porn mode, you can open a tab that saves no history. Great, the politician’s dream.

“It’s good for developers because it’s open source” That’s debatable. My ultimate question is: can you get more standardization by further segmenting the market? I doubt it, they have to be counting on wiping out the competition.

Popularity: 4% [?]

Comments

Comment from Douglas Karr
Time: September 1, 2008, 9:12 pm

Of course, by starting with WebKit, they aren’t giving designers and marketers too many issues to work around. Out of the box, it your code is working with Safari and Firefox, you should be good to go with Chrome. Seems like what they are really trying to accomplish is building the first step to an OS to run all of their SaaS applications within efficiently.

Comment from Christopher S. Penn
Time: September 1, 2008, 9:35 pm

The key here is threading – by forking the browser constantly, Google hopes that things like Gears can be more efficient. It’s a solution to a problem they have with Docs and other apps.

Turn the page:

« | Home | »