Linked by Kroc Camen on Tue 24th Feb 2009 14:55 UTC
Apple released the Safari 4 Beta today. Features: Tabs on top. "Top Sites" 'Speed Dial' feature. "Smart" address/search fields. HTML5 Canvas. HTML5 Audio/Video (though no Ogg). Acid 3. CSS Animation/Gradients/Masks/Reflection. CSS Web Fonts. New "Nitro" Javascript engine - "Up to 4 times faster than Firefox 3.1". 'Native' look and native font rendering on Windows Vista/XP. I can think of only one thing: "Now witness the firepower of this fully armed and operational battle station!"
Thread beginning with comment 350456
To read all comments associated with this story, please click here.
To read all comments associated with this story, please click here.
RE: Safari still a memory pig? No crash protection?
by someone on Wed 25th Feb 2009 02:44
in reply to "Safari still a memory pig? No crash protection?"
Member since:2006-01-12
Another reason is that Safari has lacked really basic things like session-save and crash protection. To get that, you have to buy Saft, which becomes a bit of a pain every time Safari gets updated. Did they fix that yet?
Have you tried History/Reopen All Windows from Last Session (available since Safari 3)?
RE[2]: Safari still a memory pig? No crash protection?
by thewolf on Wed 25th Feb 2009 10:04
in reply to "RE: Safari still a memory pig? No crash protection?"
Member since:2007-12-27
Recent Original Stories
Recent Comments
Headlines
Random Comments
Random Stories
Random OS Link
Member since:
2006-03-02
One reason I switched from Safari to Firefox, despite the fact that I miss some of the usability features is that Safari was a huge memory pig. It would use on the order of 3x the memory of Firefox for the same thing, and yes, I am taking into consideration the fact that Firefox will return pages to the OS while Safari will not. I bet they haven't done a damn thing about memory usage.
Another reason is that Safari has lacked really basic things like session-save and crash protection. To get that, you have to buy Saft, which becomes a bit of a pain every time Safari gets updated. Did they fix that yet?