Slashdot Mirror
Safari 4 Released, Claimed "30 Times Faster Than IE7"
CNETNate writes "Apple has released the beta version of Safari 4 for Mac and PC, with claims that its Nitro rendering engine is '30 times faster than IE7,' and three times faster than Firefox 3. Other new features include 'Top Sites,' which shows users the most frequently visited Web pages, 'Full History Search' for searching through not only the URLs and titles of visited pages, but also the complete text within the page itself — something Opera has been doing for a while."
Anyone know if this is a new engine or just Squirrelfish renamed?
Looks like Safari might be the first Acid 3 browser to the market. Opera's version 10 is Acid 3 compliant, but it's still in Alpha testing.
I noted this feature in Opera 10. The results shown in the demos were rather impressive. The web pages had more of a print-layout look to them without the classic trick of relying on images to cover all the content. This has the potential to completely change the look of the web for the better.
I'm still trying to figure out how being able to use Canvas as a style to apply to web elements is useful, but the idea definitely sounds cool. I suppose one could always set a fixed web page background as a canvas, then make it look like they're on an acid trip as they scroll. :-P
I'm downloading the beta now. If it lives up to the hype that Apple is giving it, it will be an amazing piece of software.
Javascript + Nintendo DSi = DSiCade
Its like saying you beat the kid with a fake leg at sprinting, or beating the a preschooler at a spelling bee.
Obligatory blog plug: http://www.caseybanner.ca/
Here's the actual claims from Apple's website:
"Using the new Nitro Engine, for example, Safari executes JavaScript up to 30 times faster than Internet Explorer 7 and more than 3 times faster than Firefox 3 based on performance in leading industry benchmark tests: iBench and SunSpider.
In addition to superior JavaScript performance, Safari offers top-flight HTML performance -- the best on any platform -- loading pages 3 times faster than Internet Explorer 7 and almost 3 times faster than Firefox 3."
I'm not too familiar with either of these benchmarking programs, so I can't really pick at the results too much, but the actual claim is 'up to 30 times faster' which means that for some function it's 30 times faster, but for most it's probably not at that level of magnitude. It seems as though some of this important information was lost in the game of telephone that is internet news.
Also, I'm more interested in how it stacks up against Firefox, Opera, and Chrome. Comparing it to IE7 is a little bit like Ford comparing their new car to a horse and cart. No offense meant to the browser, but from every chart I've seen it's the bottom of the barrel in terms of speed.
If IE and Safari can look at Firefox's source code and see exactly how FF implement's something, how can FF maintain a competitive advantage as a core browser. By core browser I mean without all the plugins/themes/extensions. IE/Safari already have a distribution advantage in that the browser comes with the OS. I'm going to a assume that the folks over at Mozilla would not declare victory if Apple/MSFT decided one day to reskin and rename FF and package it with their OS.
It's a unfair advantage that the OS vendors can see the source code of FF, however the reverse is not true. So if Safari has this great performance, how can the FF figure out how Safari does it?
http://www.apple.com/safari/features.html - Safari 4 introduces the Nitro JavaScript engine, an advanced bytecode JavaScript engine that makes web browsing even faster. In fact, Safari 4 executes JavaScript up to 6 times faster than Internet Explorer 8 and up to 4 times faster than Firefox 3.1.
So if Safari has this great performance, how can the FF figure out how Safari does it?
By heading over to WebKit.org and downloading the open source rendering engine it uses?
Given that this alleges to be a beta version and according to its own EULA:
why do Apple insist on removing any existing Safari 3 install when installing?
If we are supposed to evaluate and develop, then surely it would be prudent to allow a stable version to also be installed alongside for mission-critical usage.
Surely it's a TERRIBLE idea for non-stable, evaluation software to disallow the use of an alternative stable version?
Apple loves to put in meaningless benchmarks with no real-world meaning to hype their products.
For example, the "3 times faster than a Pentium II" claims back in some of the older PowerPC days - this was true for a single Photoshop operation that at that point had Altivec optimizations on PPC but was running straight scalar code (no MMX) on a P2.
For nearly all other applications, the P2 was equal to or faster than the PPC. But Apple hyped their systems based on that one single meaningless-for-most-people benchmark. (As opposed to AMD's speed rating system which for the Athlon XPs was based on a suite of benchmarks and their average comparison to a similarly clocked P4, which was typically pretty accurate.)
Here, how is Apple magically eliminating network latency and providing infinite network bandwidth with browser changes? For nearly all users, the network is the bottleneck.
retrorocket.o not found, launch anyway?
Falling Leaves Animation: http://webkit.org/blog-files/leaves/index.html
Bouncing Box Animation: http://webkit.org/blog-files/bounce.html
Rotate and Fade Animation: http://webkit.org/blog-files/pulse.html
CSS Recipes for Effects: http://developer.apple.com/safari/articles/webcontent/cssrecipes.html
CSS Gradients: http://developer.apple.com/safari/library/documentation/InternetWeb/Conceptual/SafariVisualEffectsProgGuide/Gradients/chapter_2_section_1.html#//apple_ref/doc/uid/TP40008032-CH7-SW11
Video tag (requires Quicktime): http://webkit.org/blog/140/html5-media-support/
CSS Gradients: http://webkit.org/blog/175/introducing-css-gradients/
Background Shaped Clipping: http://webkit.org/blog/164/background-clip-text/
Local Database Example: http://webkit.org/misc/DatabaseExample.html
Javascript + Nintendo DSi = DSiCade
- Scrolling this /. page is extremely slow in safari.
- The tabs in the window's title bar is just plain annoying and feels really out of place.
- Just like Google's Chrome this browser also doesn't blend in well with MS Windows UI. It's feels alien to the other programs.
I've tried pointing that out before, but you're probably wasting your breath. The tin-foil hat crowd here at slashdot seems to think that Apple is keeping all the juiciest enhancements for themselves. I know it's not true because I run Safari on my macs and have run some webkit browsers like midori on my linux machines, they're about as fast, certainly faster than firefox. I'd use midori as my full time browser, but it's not as full featured as firefox and is unstable (or was last version I downloaded, like 0.0.21 or so).
Gentlemen! You can't fight in here, this is the war room!
For anyone that has both a Mac and PC, one of the minor frustrations you face is constantly having to remember to use different keyboard shortcuts when you move back and forth. Safari on the PC was an option for me for this reason alone. Sadly, the Mac-look, odd window handling, terrible font rendering and random long pauses (something to do with advertisements I think) made it an option only - I had to keep Chrome and FF around for some sites.
No longer. Safari 4 is now my default Windows browser. And not just because of the keystrokes, it's faster than any of the other (always up-to-date) browsers on this machine, renders everything perfectly (Chrome still has serious problems here), the font problems are gone (now Chrome is the one that looks bad), the random pauses are missing, etc.
So basically Safari now does everything any of the other browsers does, plus more, plus its faster, AND it has the same keystrokes.
Still not perfect though: I'm still trying to get the font sizes right (the readable text above is fine, but this editor has HUGE text) and I want to remove the Chrome-like tools menus (I like real menu bars, thanks), and there's some oddity when scrolling long pages. But nevertheless the problems are less than those in Chrome and the speed of FF in comparison makes me willing to overlook them.
Maury
Maybe you do, but I shave to keep my ballsack silky.
And just because you have to design for the LCD doesn't mean you have to always use the LCD. Life is short. Use a better browser. I don't care which one, but only stoop to the LCD when you absolutely have to.
The "cue the foo posts in 3, 2, 1..." posts will commence with no subsequent foo posts in 3, 2, 1...
Opera 10 has been out months with these features, and it's javascript speed is very good on REAL WORLD SITES, not just the Webkit optimized SunSpider synthetic benchmark...
During the early days of Safari 3.0, I was in charge of making sure my companies product was compatible with Safari.
I have built WebKit from their xcode project. I have submitted bugs. And I know that sometimes the fix arrives in Safari months before WebKit.
I have much respect for that development team, but to say that Apple (as close-lipped and proprietary as they are) isn't holding anything back is just naive.
Online Starcraft RPG? At
Dietary fiber is like asynchronous IO-- Non-blocking!
I switched to Firefox for two reasons. One is that Safari is a major memory hog. It can use like 3x the memory as Firefox for the same thing. (And I'm talking about fresh starts. I know all about how VMs can swap unused pages to disk.)
The other missing thing from Safari was something as basic as session saving and crash protection. You have to buy Saft for that. With Firefox, it's free.
I wonder if Apple has done anything about these issues.
Requirements:
Mac with an Intel processor or a Power PC G5, G4, or G3 processor and built-in FireWireî
um, looks like the latest Macbook isn't up to spec. nice one, Apple.
The big problem Safari faces is that Opera users already dominate the snobby-over-nothing niche Apple usually occupies :-(
// MD_Update(&m,buf,j);
The session *is* saved, and you can restore it using History - Reopen All Windows From Last Session.
If you want this to happen automatically when Safari starts up, you could install SafariStand, which does this and a whole lot more for free.
As for the memory issues... I don't know which browser uses more memory, but I sure know which one feels slow and unresponsive on my machine, and it's not Safari.
/var/run/twitter.sock is a twitter socket puppet.
The latest safari nightly (r41176) compiles and runs just fine on my stock Ubuntu Hardy box. The only pain I encountered was the libsoup 2.25 library dependency which I had to pull down and compile myself instead of using the older library supplied from the Hardy repository.
Not only is WebKit open-source, it also seems like Apple has gone to great length to ensure that this piece of software is portable to other operating systems. The key is to actually do the "wget, autogen.sh, make, make install" steps yourself. It's really not that hard.
As a developer working on WebKit, this is completely wrong and more than a little insulting.
The versions of WebKit included with Safari releases are built directly from the public tree. There is no secret version of WebKit that Apple fixes bugs in for Safari releases before eventually landing the changes in the WebKit tree. The WebKit tree is Apple's official WebKit tree, and is where all of Apple's development on WebKit for Mac OS X and Windows takes place.
For sake of reference http://trac.webkit.org/browser/releases/Apple/Safari%204%20Public%20Beta contains the exact source code of WebKit that was built and released as Safari 4 Public Beta earlier today. There are no secret changes in the version of WebKit that Apple shipped. The changes are all there in the open for the world to see.