Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
Haha, I'd be fine with either of those options. :D How is it that people still use IE anyway?

I think a lot of people still don't know or care very much about browsers - they use what came on their PC and to them it's just "the internets".:eek:
I have no idea why people think this is a good browser, possibly just because of the brand recognition, but due to it's excessive popularity (which actually took Google a bit off guard) they are going to make one for Mac now. If all the dummies out there weren't drooling over it, they might never have got off the ground with it. If people reacted to products like this in a rational way instead of getting all rabid about how Google will "smack down" Safari or some such, it probably would be as popular as Opera, which is to say a niche product of limited acceptance.

So what don't you like about Chrome?
 
Google always knew this was going to be a little by little game, and slowly, with the release onto OSX and Linux, and probably mobile devices in future, they will slowly creep up as well. Shame that the worst browser is still the most used.

It's already on a mobile device -- the Android platform, currently represented by the T-mobile G1.
 
I'm quite sure they planned to release it for win/mac/linux right from the start. It's just that they put more resources on getting it out for Windows first since it has the largest user base.

This is probably not the case. It's more likely that Picasa and Chrome started out as a Windows-only project, probably by some engineers working on their 20% projects. Thus the initial choice of toolkit does not lend itself well to doing Mac and Linux ports.

Picasa ended up being released for Linux by using Wine, the reimplementation of Windows libraries; the Mac version is now in beta, but I have not checked it to discover how they implemented it -- probably Wine as well.

Contrast this with Google Earth, which was written using Trolltech's (now Nokia's) Qt framework. It is available natively for Windows, Mac and Linux.
 
That and the remaining just don't care. As long as I can get to a site quickly, have it rendered as intended and have tabs, I don't care what I'm using. So far it's Safari with AdBlock and Saft.

Yep, that's a fair point as well - many poeple (not you btw) don't care about features, stability and security - those aspects of web browser technology are transparent to them and as long as the browser does what they want it to do, they couldn't care less if it loads .5 seconds slower than another browser, has a smaller footprint, etc.
 
I think it will be a long time coming before Chrome supports a plug-in framework. Not only do they introduce memory leaks from poorly written code by 3rd party developers (yes, running in separate processes helps here) but the most popular plug-ins for Firefox are AdBlock Plus and FlashBlock (I certainly wouldn't browse without either)...

Now, Google makes their money of advertisements (yes, I don't really mind the text ads on the side of search results and I don't think AdBlock Plus fux0rz with these ads). That being said Google did buy "affiliates" like DoubleClick which were the main cause of plug-ins like AdBlock Plus to be made in the first place.

God help me, I do not want another browser to test on, with its own quirks and problems. Google, just throw money at Firefox or sabotage IE, please.

I believe it uses the latest and greatest version of WebKit so if you can get it to work in Safari, it should look great in Chrome. On top of that, it will be ACID3 compliant.
 
i'd only use chrome if it had something similar to adblock and video download helper, addons that firefox have. thats the main reason i use firefox lol.

i prefer safari > firefox, webpages just seem to look far better, but because of the lack of addons and such i tend to stick to FF.

i never tried chrome on my PC, just didn't appeal to me. might try it when its out for os x though.
 
From my experience with Chrome (PC) it is a nice product but has a little way to go before it's get me to use it everyday. Hopefully, Mac Chrome will be better.
 
For some reason Internet Explorer, Safari and FF have all given me problems on my PC.. in one form or another, often times freezing my computer.

Ever since I had Chrome (About 5 weeks maybe more) I have had no problems with it other than the occasional website that doesn't load, but the interface of Chrome is so smooth and fast that it is a breeze to fix.

I love Chrome!!
 
Good, it'll be out. But I won't use it. The UI is abhorrent in Windows and I hate how it has that silly start page of your most visited pages.

You understand there is an option to use the "old" homepage right?
 
I do adore Google Chrome, but I'm currently too comfortable with Firefox to make a complete jump. Nevertheless I am excited to see Chrome being released for Mac in the next five month or so. I'll probably download it the moment it's release ... that is, if I actually own a Macbook by that time.
 
This is probably not the case. It's more likely that Picasa and Chrome started out as a Windows-only project, probably by some engineers working on their 20% projects. Thus the initial choice of toolkit does not lend itself well to doing Mac and Linux ports.

Picasa ended up being released for Linux by using Wine, the reimplementation of Windows libraries; the Mac version is now in beta, but I have not checked it to discover how they implemented it -- probably Wine as well.

Contrast this with Google Earth, which was written using Trolltech's (now Nokia's) Qt framework. It is available natively for Windows, Mac and Linux.

Not all of Google's (or Apple's, for that matter) technology is home-grown. Picasa came from an acquisition of its original developer, as did some of the technology behind Maps/Earth. The Mac version of Picasa is native, BTW.

Though it drives web developers mad, browser competition is a good thing for users. If Firefox hadn't reignited the browser wars, the IE-ruled web would have been a dismal place.

That said, I'll play with Chrome on an test drive, since I'm a browser whore, but neither it, nor any other Google app will be allowed on my main drive as long as they continue to distribute their apps with their hidden daemons.
 
I'm perfectly happy with the browsers I have now (Opera and FF) and see no need to switch browsers, especially to one with a EULA like Chrome's (or did they finally see the light and take out that bit about Google owning copyright on anything you make using their browser?).
 
I'm perfectly happy with the browsers I have now (Opera and FF) and see no need to switch browsers, especially to one with a EULA like Chrome's (or did they finally see the light and take out that bit about Google owning copyright on anything you make using their browser?).

If by "finally" you mean "very shortly after it was noticed", then yes. It was just a mistake (I talked with the guy responsible for it).
 
Ya I was looking at that and I thought of compiling it for myself but I dont think the result will be what I expect. Im not that experienced in that area. Im gonna search for a how to, see if I can find info about it.

EDIT: After reading more on Chrome's dev page, it seems that at the moment they have the current build rendering pages but no UI. The UI will be out in Q1 of 09 but no sooner. But I believe it's gonna be written in Cocoa.

Building is not that complicated, but it does take some time to set up the right tools. But if you want to have a look: I regularly post up-to-date binaries on this page. There is a "UI", but it doesn't include things like bookmark management, tabs, etc.
 
Building is not that complicated, but it does take some time to set up the right tools. But if you want to have a look: I regularly post up-to-date binaries on this page. There is a "UI", but it doesn't include things like bookmark management, tabs, etc.

Thanks, I'll check it out. But at it's current state, I don't think its worth it for me, yet...
 
I think it will be a long time coming before Chrome supports a plug-in framework. Not only do they introduce memory leaks from poorly written code by 3rd party developers (yes, running in separate processes helps here) but the most popular plug-ins for Firefox are AdBlock Plus and FlashBlock (I certainly wouldn't browse without either)...

Now, Google makes their money of advertisements (yes, I don't really mind the text ads on the side of search results and I don't think AdBlock Plus fux0rz with these ads). That being said Google did buy "affiliates" like DoubleClick which were the main cause of plug-ins like AdBlock Plus to be made in the first place.

no, sorry to burst YOUR bubble

http://news.cnet.com/8301-17939_109-10110247-2.html
 
I don't like Chrome, i think it sucks. It has a very crappy design and Firefox is just the best one i've come across so.. I don't think that Chrome will be a big hit..

No Chrome does not 'Suck'. It is probably a browser not for you. It isn't that much for me either. I use FF for its great themes and add-ons. Hope google can measure up to Firefox standards.:rolleyes:
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.