<?xml version="1.0" encoding="utf-8"?>
<rss xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title>satine.org - Latest Comments in satine.org  &amp;raquo; SquirrelFish Extreme: Fastest JavaScript Engine Yet</title><link>http://satine.disqus.com/</link><description></description><atom:link href="https://satine.disqus.com/satineorg_raquo_squirrelfish_extreme_fastest_javascript_engine_yet/latest.rss" rel="self"></atom:link><language>en</language><lastBuildDate>Fri, 20 Feb 2009 08:14:58 -0000</lastBuildDate><item><title>Re: satine.org  &amp;raquo; SquirrelFish Extreme: Fastest JavaScript Engine Yet</title><link>http://www.satine.org/archives/2008/09/19/squirrelfish-extreme-fastest-javascript-engine-yet/#comment-6429010</link><description>&lt;p&gt;Firefox is approximately twice as slow as Chrome, and Safari 4.0 was approximately 1.33x as slow as FF.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Exteme Mobile Phone Spy</dc:creator><pubDate>Fri, 20 Feb 2009 08:14:58 -0000</pubDate></item><item><title>Re: satine.org  &amp;raquo; SquirrelFish Extreme: Fastest JavaScript Engine Yet</title><link>http://www.satine.org/archives/2008/09/19/squirrelfish-extreme-fastest-javascript-engine-yet/#comment-6392985</link><description>&lt;p&gt;This is interesting because it shows how fast Javascript can go. All we need now is a good web framework similar to Rails or Django, but based on JS. Then server-side JS can take off.&lt;/p&gt;&lt;p&gt;One thing these tests don't take into account is when you have multiple tabs open in FF or IE, memory does leak a lot, and one hung script can bring down all tabs. Just like Windows 3.1 or Windows 95 from 15 years ago. Because of this, I still prefer Google Chrome because of its one-process-per-tab model. However, many browsers will do the same within the next 18 months, and then JS speed will become the next performance factor.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Jay Godse</dc:creator><pubDate>Mon, 02 Feb 2009 01:38:51 -0000</pubDate></item><item><title>Re: satine.org  &amp;raquo; SquirrelFish Extreme: Fastest JavaScript Engine Yet</title><link>http://www.satine.org/archives/2008/09/19/squirrelfish-extreme-fastest-javascript-engine-yet/#comment-6392979</link><description>&lt;p&gt;Hi,&lt;/p&gt;&lt;p&gt;Charles Ying compiles a few more comparisons&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">e-okul</dc:creator><pubDate>Thu, 25 Dec 2008 05:58:15 -0000</pubDate></item><item><title>Re: satine.org  &amp;raquo; SquirrelFish Extreme: Fastest JavaScript Engine Yet</title><link>http://www.satine.org/archives/2008/09/19/squirrelfish-extreme-fastest-javascript-engine-yet/#comment-6392996</link><description>&lt;p&gt;@gigi: I believe one of the links in the comments above mentions that IE is about 8 times slower for JS than the slowest implementation of the other major browsers. IE is (and probably always will be) a lumbering monster that seems incapable of keeping up with it's competition.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Tony Arnold</dc:creator><pubDate>Mon, 22 Sep 2008 10:06:55 -0000</pubDate></item><item><title>Re: satine.org  &amp;raquo; SquirrelFish Extreme: Fastest JavaScript Engine Yet</title><link>http://www.satine.org/archives/2008/09/19/squirrelfish-extreme-fastest-javascript-engine-yet/#comment-6392995</link><description>&lt;p&gt;And why they don't test it vs Internet Explorer? I think IE it's the fastest.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">gigi</dc:creator><pubDate>Sun, 21 Sep 2008 12:50:15 -0000</pubDate></item><item><title>Re: satine.org  &amp;raquo; SquirrelFish Extreme: Fastest JavaScript Engine Yet</title><link>http://www.satine.org/archives/2008/09/19/squirrelfish-extreme-fastest-javascript-engine-yet/#comment-6392994</link><description>&lt;p&gt;It would be nice to see the scores of each individual tests since different real world web applications use javascript differently.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">pingooo</dc:creator><pubDate>Sun, 21 Sep 2008 02:51:57 -0000</pubDate></item><item><title>Re: satine.org  &amp;raquo; SquirrelFish Extreme: Fastest JavaScript Engine Yet</title><link>http://www.satine.org/archives/2008/09/19/squirrelfish-extreme-fastest-javascript-engine-yet/#comment-6392993</link><description>&lt;p&gt;"Speed is not everything and we are not suckers for browsing speed. We want functionality!"&lt;/p&gt;&lt;p&gt;In the case of JS, speed &lt;i&gt;is&lt;/i&gt; functionality. You can make so much better and more complicated web apps if the underlying engine - JS, can handle so much more than before.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">DaVince</dc:creator><pubDate>Sat, 20 Sep 2008 19:40:58 -0000</pubDate></item><item><title>Re: satine.org  &amp;raquo; SquirrelFish Extreme: Fastest JavaScript Engine Yet</title><link>http://www.satine.org/archives/2008/09/19/squirrelfish-extreme-fastest-javascript-engine-yet/#comment-6392992</link><description>&lt;p&gt;it's funny, the more i use Chrome (for windows), the more unstable it seems to get... crashes a lot more, can't handle sites with flash, hangs every time i close a tab... all that to say, i'm switching back to Firefox&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">movie fan</dc:creator><pubDate>Sat, 20 Sep 2008 19:06:54 -0000</pubDate></item><item><title>Re: satine.org  &amp;raquo; SquirrelFish Extreme: Fastest JavaScript Engine Yet</title><link>http://www.satine.org/archives/2008/09/19/squirrelfish-extreme-fastest-javascript-engine-yet/#comment-6392990</link><description>&lt;p&gt;Oh.  Duh.  They're right there.  I look like a moron now. :)&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">buddyglass</dc:creator><pubDate>Sat, 20 Sep 2008 14:26:33 -0000</pubDate></item><item><title>Re: satine.org  &amp;raquo; SquirrelFish Extreme: Fastest JavaScript Engine Yet</title><link>http://www.satine.org/archives/2008/09/19/squirrelfish-extreme-fastest-javascript-engine-yet/#comment-6392991</link><description>&lt;p&gt;Charles, I posted my numbers last night, but Wordpress seems to have eaten the posts.  Either that, or they were too long.  Let me know if I should try to post them again.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">buddyglass</dc:creator><pubDate>Sat, 20 Sep 2008 14:25:30 -0000</pubDate></item><item><title>Re: satine.org  &amp;raquo; SquirrelFish Extreme: Fastest JavaScript Engine Yet</title><link>http://www.satine.org/archives/2008/09/19/squirrelfish-extreme-fastest-javascript-engine-yet/#comment-6392973</link><description>&lt;p&gt;So I just finished testing, and my results match up more with yours than with what I remember from the last round of testing I did.  Now that I think of it, though, I may have done my earlier tests on an iMac (Core 2 Duo) running XP inside a Parallels VM.  Maybe Chrome takes better advantage of the two cores on that system?  Or maybe I'm just on crack.  Here are my results, with links:&lt;/p&gt;&lt;p&gt;Webkit: r36682 (9/20) + Safari 3.1.2 (525.21)&lt;br&gt;Minefield: 3.1b1pre (9/20), JIT Enabled&lt;br&gt;Chrome: 0.2.149.30&lt;/p&gt;&lt;p&gt;SunSpider:&lt;br&gt;Webkit: 2814.0ms (&lt;a href="http://tinyurl.com/4fwloh)" rel="nofollow noopener" target="_blank" title="http://tinyurl.com/4fwloh)"&gt;http://tinyurl.com/4fwloh)&lt;/a&gt;&lt;br&gt;Minefield: 2767.4ms (&lt;a href="http://tinyurl.com/4z8gv4)" rel="nofollow noopener" target="_blank" title="http://tinyurl.com/4z8gv4)"&gt;http://tinyurl.com/4z8gv4)&lt;/a&gt;&lt;br&gt;Chrome: 3316.8ms (&lt;a href="http://tinyurl.com/3osox2)" rel="nofollow noopener" target="_blank" title="http://tinyurl.com/3osox2)"&gt;http://tinyurl.com/3osox2)&lt;/a&gt;&lt;/p&gt;&lt;p&gt;Dromaeo:&lt;br&gt;Webkit: 11346.40ms (&lt;a href="http://dromaeo.com/?id=43093)" rel="nofollow noopener" target="_blank" title="http://dromaeo.com/?id=43093)"&gt;http://dromaeo.com/?id=43093)&lt;/a&gt;&lt;br&gt;Minefield: 13321.00ms (&lt;a href="http://dromaeo.com/?id=43094)" rel="nofollow noopener" target="_blank" title="http://dromaeo.com/?id=43094)"&gt;http://dromaeo.com/?id=43094)&lt;/a&gt;&lt;br&gt;Chrome: 16296.00ms (&lt;a href="http://dromaeo.com/?id=43089)" rel="nofollow noopener" target="_blank" title="http://dromaeo.com/?id=43089)"&gt;http://dromaeo.com/?id=43089)&lt;/a&gt;&lt;/p&gt;&lt;p&gt;V8 (higher is better):&lt;br&gt;Webkit: approx. 480 (varies)&lt;br&gt;Minefield: (fails)&lt;br&gt;Chrome: approx. 880 (varies)&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">buddyglass</dc:creator><pubDate>Fri, 19 Sep 2008 22:51:23 -0000</pubDate></item><item><title>Re: satine.org  &amp;raquo; SquirrelFish Extreme: Fastest JavaScript Engine Yet</title><link>http://www.satine.org/archives/2008/09/19/squirrelfish-extreme-fastest-javascript-engine-yet/#comment-6392975</link><description>&lt;p&gt;True, the Safari 4.0 beta didn't have the latest version of Squirrelfish.  But I was using a nightly build of FF3.1 as of approximately 3 weeks ago, and testing vs. the initial release of Chrome.  You have FF handily beating Chrome on Dromaeo, which was the reverse of what I saw.  I'll download nightlies of FF and Webkit, and test vs. the latest Chrome, on SunSpider, Dromeaeo and Google's V8 tester.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">buddyglass</dc:creator><pubDate>Fri, 19 Sep 2008 21:37:30 -0000</pubDate></item><item><title>Re: satine.org  &amp;raquo; SquirrelFish Extreme: Fastest JavaScript Engine Yet</title><link>http://www.satine.org/archives/2008/09/19/squirrelfish-extreme-fastest-javascript-engine-yet/#comment-6392977</link><description>&lt;p&gt;buddyglass: Safari 4.0 (I assume you're using 4.0 Developer Preview) is not the latest version of Safari + WebKit. The 3 browsers I'm comparing are using the latest nightly builds taken from last night, 2008-09-18. I'd be interested to see your comparison using the latest builds on your system.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Charles Ying</dc:creator><pubDate>Fri, 19 Sep 2008 21:27:01 -0000</pubDate></item><item><title>Re: satine.org  &amp;raquo; SquirrelFish Extreme: Fastest JavaScript Engine Yet</title><link>http://www.satine.org/archives/2008/09/19/squirrelfish-extreme-fastest-javascript-engine-yet/#comment-6392978</link><description>&lt;p&gt;I'm not sure what sort of system you used, but when I tested the three browsers on Windows XP running on a 2.4ghz P4, I found that Chrome totally smoked FF and Safari 4.0 (not using Squirrelfish  Extreme) on Dromaeo.&lt;/p&gt;&lt;p&gt;FF was approximately twice as slow as Chrome, and Safari 4.0 was approximately 1.33x as slow as FF.&lt;/p&gt;&lt;p&gt;Chrome also performed ridiculously better on Google's own V8 tuning benchmark:&lt;/p&gt;&lt;p&gt;&lt;a href="http://code.google.com/apis/v8/run.html" rel="nofollow noopener" target="_blank" title="http://code.google.com/apis/v8/run.html"&gt;http://code.google.com/apis...&lt;/a&gt;&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">buddyglass</dc:creator><pubDate>Fri, 19 Sep 2008 21:13:36 -0000</pubDate></item><item><title>Re: satine.org  &amp;raquo; SquirrelFish Extreme: Fastest JavaScript Engine Yet</title><link>http://www.satine.org/archives/2008/09/19/squirrelfish-extreme-fastest-javascript-engine-yet/#comment-6392989</link><description>&lt;p&gt;It would indeed be nice to see a slower (e.g. IE) JS engine compared to it, even if its bar is so small it's unreadable. It'd be a great demonstration of the amount of progress made in a small amount of time.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Vincent</dc:creator><pubDate>Fri, 19 Sep 2008 17:30:33 -0000</pubDate></item><item><title>Re: satine.org  &amp;raquo; SquirrelFish Extreme: Fastest JavaScript Engine Yet</title><link>http://www.satine.org/archives/2008/09/19/squirrelfish-extreme-fastest-javascript-engine-yet/#comment-6392972</link><description>&lt;p&gt;I think Oliver was talking about Chrome's independent process model that lets Chrome survive Flash crashes, as well as any others for plugins. Which would be nice to see in Safari.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Another Jon</dc:creator><pubDate>Fri, 19 Sep 2008 16:39:19 -0000</pubDate></item><item><title>Re: satine.org  &amp;raquo; SquirrelFish Extreme: Fastest JavaScript Engine Yet</title><link>http://www.satine.org/archives/2008/09/19/squirrelfish-extreme-fastest-javascript-engine-yet/#comment-6392988</link><description>&lt;p&gt;Jon:&lt;/p&gt;&lt;p&gt;IE8 is ~ 10 times slower than the others.&lt;br&gt;So it doesn't really qualify for this benchmark.. It would only make the bar graph unreadable.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Enola</dc:creator><pubDate>Fri, 19 Sep 2008 16:29:02 -0000</pubDate></item><item><title>Re: satine.org  &amp;raquo; SquirrelFish Extreme: Fastest JavaScript Engine Yet</title><link>http://www.satine.org/archives/2008/09/19/squirrelfish-extreme-fastest-javascript-engine-yet/#comment-6392987</link><description>&lt;p&gt;Why don't you include IE8 in these benchmarks?  As a web developer I am loving the focus on javascript performance for the next generation of browsers, but IE is always a [limiting] factor in terms of knowing how far I can push the browser.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Jon</dc:creator><pubDate>Fri, 19 Sep 2008 14:37:02 -0000</pubDate></item><item><title>Re: satine.org  &amp;raquo; SquirrelFish Extreme: Fastest JavaScript Engine Yet</title><link>http://www.satine.org/archives/2008/09/19/squirrelfish-extreme-fastest-javascript-engine-yet/#comment-6392980</link><description>&lt;p&gt;Maybe Oliver's point was that Adobe should pull their fingers out of their buts and do some optimisation of Flash on Mac OS X. It that wasn't Oliver's point, then it can be mine instead.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Andy</dc:creator><pubDate>Fri, 19 Sep 2008 12:38:21 -0000</pubDate></item><item><title>Re: satine.org  &amp;raquo; SquirrelFish Extreme: Fastest JavaScript Engine Yet</title><link>http://www.satine.org/archives/2008/09/19/squirrelfish-extreme-fastest-javascript-engine-yet/#comment-6392981</link><description>&lt;p&gt;@oliver&lt;/p&gt;&lt;p&gt;It sounds like you have a chip on your shoulder. There's plenty that can contribute to an unstable browser. If you can point me to a flash file that will crash a given browser *every* time for everyone, then your point will stand. If it only affects your system, then you have somewhere to start to solve the problem.&lt;/p&gt;&lt;p&gt;Way to go WebKit Team! This is fantastic. &lt;a href="http://280slides.com" rel="nofollow noopener" target="_blank" title="280slides.com"&gt;280slides.com&lt;/a&gt; runs amazingly well in the latest WebKit nightly.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Ted Wood</dc:creator><pubDate>Fri, 19 Sep 2008 12:10:11 -0000</pubDate></item><item><title>Re: satine.org  &amp;raquo; SquirrelFish Extreme: Fastest JavaScript Engine Yet</title><link>http://www.satine.org/archives/2008/09/19/squirrelfish-extreme-fastest-javascript-engine-yet/#comment-6392986</link><description>&lt;p&gt;Damian: Oops, no the Windows test system is on different (slower) hardware. I suppose I should try it on the same hardware, but I don't have Bootcamp on this iMac. I'll try a Parallels version soon and post the results here.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Charles Ying</dc:creator><pubDate>Fri, 19 Sep 2008 11:46:56 -0000</pubDate></item><item><title>Re: satine.org  &amp;raquo; SquirrelFish Extreme: Fastest JavaScript Engine Yet</title><link>http://www.satine.org/archives/2008/09/19/squirrelfish-extreme-fastest-javascript-engine-yet/#comment-6392983</link><description>&lt;p&gt;Yay progress!&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">ethana2</dc:creator><pubDate>Fri, 19 Sep 2008 10:02:01 -0000</pubDate></item><item><title>Re: satine.org  &amp;raquo; SquirrelFish Extreme: Fastest JavaScript Engine Yet</title><link>http://www.satine.org/archives/2008/09/19/squirrelfish-extreme-fastest-javascript-engine-yet/#comment-6392982</link><description>&lt;p&gt;Who cares for JS speed as long as the browser can be crashed by Flash content.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">oliver</dc:creator><pubDate>Fri, 19 Sep 2008 09:59:56 -0000</pubDate></item><item><title>Re: satine.org  &amp;raquo; SquirrelFish Extreme: Fastest JavaScript Engine Yet</title><link>http://www.satine.org/archives/2008/09/19/squirrelfish-extreme-fastest-javascript-engine-yet/#comment-6392984</link><description>&lt;p&gt;Your charts show Safari Windows at 7.9 to and Safari on OS X at 13.7 -- are these on the same hardware? On the face of it it looks like there is something surprisingly slow about the Windows version...&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Damian Cugley</dc:creator><pubDate>Fri, 19 Sep 2008 08:22:53 -0000</pubDate></item></channel></rss>