Alright, haven’t posted anything to by blog for little over 9 months now and it is time to get back. And what better way to do that to follow up on the last post.
It was about Google Chrome and I had put up 4 complaints. All those complaints were resolved quickly somehow (not because of my post though) and I am still a happy Chrome user at office where I have a Windows PC. I am on Dev Channel, hence get updates every few days and it mostly works for what I do.
At home is different story now. I’ve switched to Mac and don’t have any Windows machine any more. (Well I have but I don’t use it!). I’ve been using FireFox and Safari on home Mac (an iMac and MacBook Pro to be precise) and just this week installed Alpha official build of Chrome. It does not work for me yet as it does not have basic things like Flash at this time.
So I am on Safari 4.0 as of today with FireFox for backup. Will love to use Chrome but not sure how long I have to wait till a working official version is released.
Google Chrome is gonna stay, big time. That is what I feel after using it for a long while. It might become 1st or 2nd most popular browser soon too. I got no hesitation to recommend using it even to novice users.
{ 4 comments… read them below or add one }
Well, do we need a CD to install Google chrome or by net?
You can download stable release from http://www.google.com/chrome.
I use Dev Channel releases which are updated weekly and are meant only for testing. If you are developer or techie, you might be interested in these early access releases available from http://dev.chromium.org/getting-involved/dev-channel
Certainly it will have a good time as far as google manages to run their GoogleUpdate.exe on your windows machine. You can get rid of this but guess what? it will be there as soon as you connect.
Its skinny and nice to compare that the amount of memory it consumes once you minus the googleupdate and per process overhead! Each tab or webpage is executed in separate process so basically you are consuming per process memory which can’t be less in any situation as compare to single process. A broken software is good to run in separate process space so ‘bugs’ wont destroy the whole app. To make it multithreaded takes more firefox source that will be done at some point.
Not to mention the heavy duty process switching that your CPU would be doing! Last but not least there are no ‘add-on-s’ you might have to wait for couple to months or years.
You are always welcome to firefox when you had enough.
Dear fireFox:
I like your long rant and am not here to debate YOU vs. Chrome. I just like Chrome and its elegance. Even the Dev channel releases (2-3 updates per week) and mostly solid.
YOU are great stable browser but Chrome is revolutionary kid on the block. Moreover me thinks that YOU are for average user, while Chrome is for nerds.