Is safari really faster? Chrome seems much faster to me.
Who said anything about it being faster? We're talking snappiness here, not speed.
Got a tip for us?
Let us know
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
Mac OS X Lion's Safari is Snappier and More Stable Thanks to WebKit2
- Thread starter MacRumors
- Start date
- Sort by reaction score
Who said anything about it being faster? We're talking snappiness here, not speed.
long time reader, first time poster
..
in the past 2 years i've tried every major browser (except opera, i simply don't like its looks, don't ask me why) available for mac os x.
long story short, after switching from safari to chrome, then back to safari, i finally decided to give firefox another chance. and i was very impressed! they had done an amazing job! firefox 4, and especially the b12, seems to be very light, youtube videos play without any problem and it seems to me that firefox is rendering the pages faster than its competitors.
there are some sites, like macrumors, which webkit based browsers have problems loading with. with safari i even got the spinning beach ball when it tried to load the page. i'm not a web guru, so i can't give you more details on that. it's just what i've experienced.
despite that, safari still got the best scrolling i've ever seen. in no other browser it's as smooth as in safari.
i really hope that this gets fixed in the next major update of safari.
in the past 2 years i've tried every major browser (except opera, i simply don't like its looks, don't ask me why) available for mac os x.
long story short, after switching from safari to chrome, then back to safari, i finally decided to give firefox another chance. and i was very impressed! they had done an amazing job! firefox 4, and especially the b12, seems to be very light, youtube videos play without any problem and it seems to me that firefox is rendering the pages faster than its competitors.
there are some sites, like macrumors, which webkit based browsers have problems loading with. with safari i even got the spinning beach ball when it tried to load the page. i'm not a web guru, so i can't give you more details on that. it's just what i've experienced.
despite that, safari still got the best scrolling i've ever seen. in no other browser it's as smooth as in safari.
i really hope that this gets fixed in the next major update of safari.
So, uhm, did you guys also feel Safari as being snappier or did you just get tangled up in something entirely unrelated?
Snappier. Take a look at my first comment
That's why Macs are so cool to begin with, when a program crashes, only that program crashes. Now, only a portion of the program will crash? GO
I find it just one feature. Their are unique features to PC's as well.
I found browning & scrolling the itune store in iTune is smoother and use less cpu too. It share the same webkit2 framework.
Yes this is something very useful.
Apple has Google to thank for many of the brilliant implementation ideas.
Attachments
I know. That's why I brought up IPC ;-).. The part of my post you're referencing was more of a reply to this:
I should have quoted it more clearly.
Wirelessly posted (Mozilla/5.0 (iPhone; U; CPU iPhone OS 4_2_1 like Mac OS X; en-us) AppleWebKit/533.17.9 (KHTML, like Gecko) Version/5.0.2 Mobile/8C148 Safari/6533.18.5)
I don't have the Lion prerelease but have been running the WebKit nightlies for just about ever now. It is very much snappier!!! More importantly WebKit nightlies render far more pages correctly than Safari 5.0.3.
As for bugs in the Previes release or WebKit for that matter, what do you guys expect? Honestly? The whole point of nightlies or prerelease like 5.1 is to find bugs, test software and prove out new concepts. There is another 5 months or so to go before Lion becomes a release product. The thing to do is to report those bugs and crashes to help Apple make a better product.
In any event the important thing to realize here is that the new WebKit process technology will be leveraged really well on those new Quad core laptops. It might take Apple a while to stabilize Safari 5.1 but it ought to be really impressive on multi core hardware. This is really a significant move away from singly threaded apps and thankfully is supported in WebKit 2 in a way that all WebKit 2 based apps can take advantage of it. Beyound that WebKit is making greater use of the GPU than ever before. In the end Safari 5.1 will be using your hardware to a greater extent than ever before. This is nice!
In any event I've gotten very use to WebKit nightlies and only run Safari 5.0 when I really need to. It really does offer up a better experience and is worth the trade off of an occasional crash. So if you are similarly inclined id reccomend the nightlies.
I don't have the Lion prerelease but have been running the WebKit nightlies for just about ever now. It is very much snappier!!! More importantly WebKit nightlies render far more pages correctly than Safari 5.0.3.
As for bugs in the Previes release or WebKit for that matter, what do you guys expect? Honestly? The whole point of nightlies or prerelease like 5.1 is to find bugs, test software and prove out new concepts. There is another 5 months or so to go before Lion becomes a release product. The thing to do is to report those bugs and crashes to help Apple make a better product.
In any event the important thing to realize here is that the new WebKit process technology will be leveraged really well on those new Quad core laptops. It might take Apple a while to stabilize Safari 5.1 but it ought to be really impressive on multi core hardware. This is really a significant move away from singly threaded apps and thankfully is supported in WebKit 2 in a way that all WebKit 2 based apps can take advantage of it. Beyound that WebKit is making greater use of the GPU than ever before. In the end Safari 5.1 will be using your hardware to a greater extent than ever before. This is nice!
In any event I've gotten very use to WebKit nightlies and only run Safari 5.0 when I really need to. It really does offer up a better experience and is worth the trade off of an occasional crash. So if you are similarly inclined id reccomend the nightlies.
And IE8 was already running with a similar sandboxing model when it showed up in Chrome.
Not in a release version they weren't.
Chrome was first with a release version with the feature. Anyway, anyone feel that all the "features" announced in Safari 5.1 are just Apple catching up to other browsers ? Seems to me they're having problems "innovating" in the browser space.
Ahh but...
That's not completely true. Every time itunes, firefox, or finder hangs on me it freezes my whole UI in 10.6.6. Until it figures everything out I have to sit there with that spinning beach ball of death.
Then again maybe I'm just running out of memory. But I have 4gb... so with the applications I'm using I figured that shouldn't be the case.
But I've never had my whole system crash like in Windows. So that's a plus.
Orange™;12009602 said:That's why Macs are so cool to begin with, when a program crashes, only that program crashes. Now, only a portion of the program will crash? GO
That's not completely true. Every time itunes, firefox, or finder hangs on me it freezes my whole UI in 10.6.6. Until it figures everything out I have to sit there with that spinning beach ball of death.
Then again maybe I'm just running out of memory. But I have 4gb... so with the applications I'm using I figured that shouldn't be the case.
But I've never had my whole system crash like in Windows. So that's a plus.
That's not true. Just switch apps with CMD+TAB or by clicking on the dock and it comes back fine with the beach balling application now being in the background.
It freezes only the menu bar, but that's normal, since the menu bar becomes part of the foreground application. It's just how the UI is made.
And seriously, Orange was wowing over Apple for nothing. fork() is not an Apple invention and it's been with us since the early Unix days. There's nothing especially amazing about tabs being forked to different processes, Unix software has been written in this manner for tens of years.
I agree. The Lion version has been very buggy for me, but I am otherwise a Safari lover. I used to like Chrome, but it has turned very sluggish, taking a long time to load pages. I often get the dialogue to force quit a tab in Chrome because the page takes too long to load.
This is incorrect, Google overtook Apple in WebKit commits late in 2009. Google is now the single largest contributor to WebKit followed by Apple. Unlike many areas where Google and Apple compete and their respective fan bases seem to butt heads - the collaboration of the teams on WebKit seems to be entirely supportive of one another and solely focused on providing the single best HTML rendering engine around, which I think anyone with a modicum of understanding of HTML/CSS will agree WebKit is far and away the most progressive and complete rendering engine available today.
How much faster can it really be ? Safari on Snow Leopard is already almost instant. I think lots are telling porkie pies.
Wow, if minor updates that do not even involve Safari can make Safari snappier, than Lion's Safari is surely about 10000000x faster! This is great news. Maybe I can download and render the page before I even think of visiting the website?
It may be snappier, and less crash-prone, but does it still consume memory like a banshee? Sometimes Safari can use up to 2.5-3 GB of RAM before I restart it (on my 12 GB/RAM iMac).
looks to be even slightly worse from what i can tell. hopefully its just debug-code bloat but we'll see
Starting with the release of Safari 4 with Snow Leopard, Safari has run plugins in a separate process so that the browser does not crash when a plugin crashes.
Tabs are not isolated from each other in the present Safari (5.0.3) so a Safari crash not related to a plugin would crash all tabs. But, most browser crashes are related to plugin crashes.
Webkit2 will have both the tabs and plugins running in separate processes. Tab crashes will not crash the browser so tabs separated like IE8. But, plugin crashes will not crash the tab as an added benefit in Safari.
Only insulating the tabs from each other does not insulate browser bugs from being exploited if crashing a plugin is the vector used to exploit the browser as the plugins still run in the browser process.
Last edited:
Not in a release version they weren't.
LOL, since it seems that Google software is in perpetual beta!
Anyway, IE8 had it in beta first, then Google followed with it in beta. Chrome V1.0 was a couple of months before IE8 RTM.
Now, three years after IE8, it shows up in a Safari beta.
LOL, since it seems that Google software is in perpetual beta!
Anyway, IE8 had it in beta first, then Google followed with it in beta. Chrome V1.0 was a couple of months before IE8 RTM.
Now, three years after IE8, it shows up in a Safari beta.
Chrome insulates both tabs and plugins. Safari, at present, insulates plugins and with the next update will insulate both as well.
IE8 only insulates the tabs. This improves the stability of the browser but offers little protection from browser exploitation because plugins run in the browser process and plugin crashes are one of the primary vectors for browser exploitation.