Permalink
Browse files

Update graphs and analysis for strict equal vs equal according to lat…

…est jsperf stats
  • Loading branch information...
1 parent 1cec754 commit aed9b7c60147336b1c1340210e4a9ea86dd4d912 timmywil committed Apr 18, 2011
View
2 css/main.css
@@ -54,7 +54,7 @@ a { color: #3355ee; display: inline-block; text-decoration: none; line-height: 1
a:hover { color: #222; border-bottom-color: #3f3f3f; }
ul { margin: 0 0 0 45px; }
-ul li { list-style: circle; padding: 10px 0 0; line-height: 1.231; }
+ul li { list-style: circle; padding: 10px 0 0; line-height: 1.1; }
ul.none { margin: 0; }
ul.none li { list-style: none; }
ol { margin: 45px 0 0 100px; }
View
BIN img/strict_equal_vs_equal.001.jpg
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
View
BIN img/strict_equal_vs_equal.002.jpg
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
View
8 index.html
@@ -229,12 +229,12 @@
</header>
<section class='lower'>
<ul>
- <li>Webkit browsers have significantly lower performance with double equal when type coercion does occur.</li>
+ <li>Chrome's V8 engine has significantly lower performance with double equal when type coercion does occur( overall performance is unmatched in V8 ).</li>
+ <li>Safari's JavascriptCore is odd. <code>==</code> wins for no type coercion and <code>===</code> wins with type coercion.</li>
<li>IE6-8 has consistently better performance with <code>===</code> whether type coercion is done or not.</li>
<li>Opera also has consistently better performance with <code>===</code>, but type coercion significantly slows both.</li>
- <li>Firefox 3.6 had the same numbers all across the board.</li>
- <li>*Exception: The new Firefox 4 js engine (jägermonkey) optimizes for ==, so it does win in this browser.</li>
- <li>Overall performance is unmatched in webkit.</li>
+ <li>Firefox 3.6's Spidermonkey had similar results to Chrome, but obviously with lower numbers.</li>
+ <li>The new Firefox 4 js engine (jägermonkey) optimizes for ==, so it does win in this browser.</li>
<li>Strict equal(===) compresses to 1 byte just like (==) with gzip compression, so the argument that it takes up more space is not valid in that case.</li>
</ul>
</section>
View
BIN strict_equal_vs_equal.key
Binary file not shown.

0 comments on commit aed9b7c

Please sign in to comment.