#Ffworks coupon code

It's super easy to run in the browser or from the command line, so you can test both pure engine performance, and the results you actually get in the browser. But at the same time, we avoided DOM tests and stuck to the core JavaScript language itself. In fact, we collected test cases from all over the web, including from other benchmarks. It's balanced between different aspects of the JavaScript language - not dominated by just a small handful of different things. Very few of the tests could be classed as microbenchmarks.

#Ffworks coupon code

It's based on real code that does interesting things both things that the web apps of today are doing, and more advanced code of the sorts we can expect as web apps become more advanced. That's why I'm particularly excited by the SunSpider benchmark: it's remarkably well thought out, easy to run, and comprehensive. The last time I looked for common JavaScript benchmarks, I came away deeply disappointed. Perhaps browser teams will begin to consider JavaScript performance a competitive advantage. The browser market is more competitive than it has been in years, with Opera 9.5, Firefox 3, Safari 3, and IE 8 all vying for the coveted default browser position.

Apple's WebKit team just announced a great new JavaScript benchmark, SunSpider.

If Web 2.0 is built on a backbone of JavaScript, it's largely possible only because of those crucial Moore's Law performance improvements.īut have we hit a performance wall? Is it possible for browsers to run JavaScript significantly faster than they do today? I've always thought that just-in-time optimizing (or even compiling) JavaScript was an unexplored frontier in browser technology. In The Day Performance Didn't Matter Any More, I found that the performance of JavaScript improved a hundredfold between 19.