Benchmarks are all over the place, but the interesting bit about this one is that this one is really spurred by Google forking the Webkit project, making its own spinoff called “Blink,” which allows it to separate itself from Apple’s Nitro JS processor, which Chrome doesn’t utilize.
Samsung (and others) end up as the odd men out though, as it uses the Apple WebKit Engine, but Chrome’s V8 JS engine. Things could get interesting going forward if these forks… well fork more.
Love this, and will be utilized as soon as I have a need for it.
Notify.js: browser dialogs never looked so good
Love this in-depth article about optimizing your web properties. I have been a proponent of a lot of this already, but there’s some new things in here I want to try and/or incorporate.
How to Lose Weight in the Browser
Hat tip, Bret
Packery: Building on Masonry
Presentations With Reveal.js and HTML5: Better Than PowerPoint
A timestamp and its milliseconds resolution isn’t always a finite enough time value. Enter Performance.now(), available in Chrome stable, Firefox 15+, and IE10.
When Milliseconds Are Not Enough: Performance.Now()
Love this write-up from over at Smashing Magaizine’s subdomain, uxdesign. It circles around on usability and where and when to use different validation techniques with your web sites’ forms.
Form-Field Validation: The Errors-Only Approach
Another nice JS-related article from over at mir.aculo.us. This one focuses on five of the things you’ve heard to never do with JS:
It might not be required, but it does make your JS quicker to scan. Plus, JSLint sure won’t be happy with your lack of semicolons.