The bottom line is that Chrome and Safari will not be sharing any less WebKit code than before - the WebCore layer, the part that does most of the heavy lifting in rendering Web content - remains unchanged. We may actually have the opportunity to share more code since we'll now be facing many of the same problems.
We also hope the Chrome team someday decides to go more in a WebKit2 direction and do multiprocess inside the WebKit API boundary instead of outside, so they can share more code with other port. But that's up to them, and they already have a lot invested in their current path.
I don't even have to open a website, just open a new tab and its starts beachballing just to load the new tab. Also extensions are a big part of my browsing experience. Safari doesn't have large extension community like firefox and Chrome.
Simply put, for me, chrome is more than its rendering engine. Overall its just a well rounded piece of software with very frequent updates, which is very unique among browsers.
defaults write com.apple.Safari DebugSnapshotsUpdatePolicy -int 2I downloaded Chrome and didn't notice anything significantly different than Safari (other than the strange-looking tabs, from the standpoint of someone used to Safari), so I shrugged my shoulders and deleted it.
I'm not saying Safari is a superior browser. Just that it has always seemed perfectly fine to me.
On an unrelated note, firefox on mac is a really sorry case. I hope this is not only on my system.
One plus to Chrome is the integrated search/URL bar, also. I've gotten so use to using the same bar for both, that I've had issues using other browsers when they try to visit some site that's actually my search query.
Firefox still has a place on my system, but it's definitely not something I want to use all the time.
In a twisted way, I'm kind of disappointed, though; it'll make the choice between Chrome and Safari a lot harder. Right now I'm using Chrome 95% of the time, but if Safari becomes much better, I might end up sitting between two chairs.
Anyone knows what the implications of this are for Chrome? They use Webkit. Will they stay on Webkit1 while Apple splits with V2?