The Burr in the Burbs

"I cling to my Lord Christ like a burr on cloth." – Katherine Luther

Thought on Google Chrome?

with 3 comments

Chrome Thought on Google Chrome?Time to compare web browsers. Do any of you web savvy browser mavens have insights into the new browser “Google Chrome?” Is it worth investigating?

I prefer Firefox over everything I’ve tried because it’s just super customizable and functional for me. Some webpages only work properly when viewed on IE, so I do keep that one around basically put I have to. I tried Safari but didn’t like it. Opera is great because it is super fast. I’ve even used Flock which is very cool for social networking. Now what about Chrome?

Written by Pastor Scott Stiegemeyer

September 25th, 2008 at 10:43 am

Posted in Uncategorized

Tagged with , , , , ,

3 Responses to 'Thought on Google Chrome?'

Subscribe to comments with RSS or TrackBack to 'Thought on Google Chrome?'.

  1. Chrome is fast, lean, and offers a nice “incognito” mode. It doesn’t handle web proxies very well, so it’s not very useful in some hotels or behind corporate firewalls.

    More info: NR article.

    Dan @ Necessary Roughness

    25 Sep 08 at 12:49 pm

  2. I’m mostly a Mac user, but I have a virtual Windows system. So I’ve used Chrome and like the simplicity of it. However, I have yet to see how it holds any advantage over Firefox.

    toddpeperkorn

    25 Sep 08 at 12:53 pm

  3. Under the hood Chrome is no different than Apple’s Safari (Windows or Mac). In fact, Google is so creative and innovative with Chrome that they’re actually using the Webkit (that’s the core of Safari) from Apple. Webkit is open source, so all they’ve done is forked it and built a new UI on it. The cool thing about Chrome, which distinguished it from the rest of the browser world is that it runs each tab as a separate process. If you’ve ever had a browser crash on you with multiple tabs open and you lose all that’s open you know of the woes of single process browser engines. Chrome essentially prevents you from losing all that, because if a page causes the renderer to crash it only kills the tab for the page that caused the crash – not the whole browser. Apart from that (which if you’re a developer is extremely cool) Chrome is nothing special.

    Stan Lemon

    25 Sep 08 at 6:07 pm

Leave a Reply

CommentLuv Enabled