Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
Disagree, if only because new features force the competition to innovate. The Google browser has some damned nice features which I would like to see in other browsers.

If only it was true... i've seen random issues with chrome that work on both firefox and safari... my ceo uses chrome, so I hear all about it.
 
Actually, Chrome uses the same rendering engine that safari does: WebKit.

1.) Chrome doesn't use the same version of Webkit as Safari.
2.) The rendering engine is just one piece of the browser puzzle. There are other pieces that differ between Chrome and Safari (e.g. the Javascript engine).
3.) It still doesn't make sense (as the other poster mentioned) to use the OS's built in web apis when the whole point of the exercise to introduce a new browser to the platform. That's like Firefox using mshtml.dll -- it just doesn't make sense.
 
Good Chrome, Bad Chrome

  1. Because Chrome is basically Safari (WebKit) under the hood, there's no good reason it shouldn't have been a breeze for them to get a Mac OS X version out the door even faster than the Windows version. There are plenty of Cocoa developers around nowadays.
  2. When have you ever had a tab crash your browser? This sounds like a solution looking for a problem, or an interesting exercise for a software engineer looking for a new challenge. If Chrome proves to be crash-proof, I'll give it another thought, but if it doesn't, I don't see the point. That said, I welcome any new browser that is built to adhere to w3c standards.
  3. Google is far from being evil. The company isn't perfect (neither is Apple), but at least they're always looking for innovation solutions to computing problems that can improve consumers' lives. Evil is when you take other companies' ideas, coopt them as your own, and then drive the original company out of business with the weight of your marketing power. Evil is when your goal is to "take over the world," not when you end up king of the hill simply because you've done such an exceptional job.
  4. If you want to use the best open source browser that's faster than Safari, download WebKit. It now has Sparkle inside for automatic updates and the latest enhancements that will eventually make their way into Safari. It's been my browser of choice for years now, and in my experience it's just as stable as Safari.
  5. I've used SafariBlock for years to block unwanted ads (including Flash) in Safari/WebKit and never had a problem. It's a great piece of freeware. Adobe Air apps run fine regardless.
  6. Since Chrome uses the same rendering and scripting engine as Safari, web designers theoretically should have nothing new to learn.
 
I probably wont use it, i rather use nightlys of webkit instead. Sure the tab thing is really really nice but i can live without it (until it's added in Safari) and i don't want googles separate updater on my mac.
 
this looks promising. i particularly like the idea of only one tab crashing/closing if the webpage has an error.
I still don't understand all the fuss about this feature. Maybe it's a common problem with IE, but I can't remember the last time a web page ever crashed on me with Safari.
 
Btw, I also HATE Chrome's fonts and font sizes. Safari's font smoothing completely blasted chrome, even on Windows.

Google is evil cause it has near complete control over browsing behavior info and info on performed searches, and it's the main ad-provider. And it's just all over the internet, spying on you. Yeah you.
 
I loved Chrome when I used it on my PC, just waiting for a Mac client to be released. When it comes to browers, Safari is right at the bottom for me, along with Internet Explorer. It seems so clunky and slow compared to Firefox (and especially compared to Chrome). Personal opinion, mind you.
 
I still don't understand all the fuss about this feature. Maybe it's a common problem with IE, but I can't remember the last time a web page ever crashed on me with Safari.

You don't surf enough. :) pages with lots of video are ones that seem to deep-6 both browsers...

"Crash" might also be a strong word. With all the ads and motion on web pages, sometimes a page 'locks up' while loading or looking for resources. When it does, you go to any other tab and do stuff - FF/Safari is just locked up until that page finishes loading.
 
1.) Chrome doesn't use the same version of Webkit as Safari.

That is irrelevant to my comment that they could have achieved the same end result using Interface Builder with no lines of code.

Any Webkit release can be dragged and dropped in Interface Builder, not just the one that came pre-installed with the OS.
 
The windows version is prettier. I'm so sick of everything on osx having that same metal finish look why can't it be blue like the windows version.

I know nothing on stability or speed or anything just that its purtty
 
1.) Chrome doesn't use the same version of Webkit as Safari.

Notice that the same is true for Safari and Mobile Safari, though. The production version of Mobile Safari has had support for the declarative CSS Animations that just landed in the WebKit nightlies last week. And yet having these different versions hasn't been a cause for alarm. Also note that Camino doesn't use the exact same version of Gecko that Firefox does. Again, no one has a panic attack about having to develop for Camino. Or Flock.

2.) The rendering engine is just one piece of the browser puzzle. There are other pieces that differ between Chrome and Safari (e.g. the Javascript engine).

V8 does not change the semantics of the JavaScript language. It is the semantics that matter to the web developer, not irrelevant minutiae about what particular optimizations the JIT attempts.

3.) It still doesn't make sense (as the other poster mentioned) to use the OS's built in web apis when the whole point of the exercise to introduce a new browser to the platform. That's like Firefox using mshtml.dll -- it just doesn't make sense.

The point is not to introduce a new browser to the platform for its own sake. The point is to introduce a browser that provides process isolation. They have no desire to introduce a new implementation of existing web standards when an excellent implementation already exists...which is why it does make complete and total sense, despite many not being able to grasp it.
 
I've seen web designers use this argument many times. The rendering engine is not a new one, it's Webkit I believe. If your page works in Safari, it should work in Chrome.

[hopefully I've remembered all that right. Someone do correct me if I'm wrong]

That is correct.

I suggest the use of chrome all the time to people who are not so tech savvy and find firefox to be either too confusing or just outright not needed. why run a slower browser for features you dont make use of afterall.

Chrome is a great browser for that purpose alone, And with its use of webkit it is much more reliable than IE.
 
This, sir, does not look like a Mac application. At all.

(But the Windows version is actually quite good.)
 
It would make absolute sense to use Webview when the whole point of a Chrome browser is to use their own engine. Idiot.



It's done that on the Windows version since day one.

Just goes to show you how long it has been since I have been on a Windows machine.
 
I tried it out on my PC a few months ago. For now I'm staying with Firefox on both platforms. When the Mac version is released I'll revisit.
 
Will not install unless you also install Google's automatic update engine for all of their software. It is described as a background process that monitors all Google update applications and updates them automatically.

I don't want this feature installed on my computer. However, Google gives no choice other than not installing any of their software. So thanks, but no thanks.
 
Yes "Genius", but in Redmond.
Yeah, I know that. I used the word 'genius' as a response to SilentCrs's ironic use of the word "idiot", not as a compliment to google.

The first IE8 beta in March 2008 has this feature.

I suppose Google's innovation, then, is to provide process isolation in a browser that's not trailing the pack in terms of conformance and performance.
 
Will not install unless you also install Google's automatic update engine for all of their software. It is described as a background process that monitors all Google update applications and updates them automatically.

I don't want this feature installed on my computer. However, Google gives no choice other than not installing any of their software. So thanks, but no thanks.

...as mentioned earlier - evil.
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.