Monthly Archives: February 2016

The future of loading CSS

With HTTP/2 asset pipelining, adding stylesheets directly above the html they affect gives you the quickest display of content from first byte.

 

It’s common to bundle all of a site’s CSS into one or two resources, meaning the user downloads a large number of rules that don’t apply to the current page. This is because sites can contain many types of pages with a variety of “components”, and delivering CSS at a component level hurts performance in HTTP/1.

This isn’t the case with SPDY and HTTP/2, where many smaller resources can be delivered with little overhead, and independently cached.

Read more from the source: jakearchibald.com

V8 JavaScript Engine: V8 Release 4.9

Chrome 49 boasts 91% ES6 support

 

In V8 release 4.9 we shipped more JavaScript ES2015 features than in any other previous release, bringing us to 91% completion as measured by the Kangax compatibility table (as of January 26). V8 now supports destructuring, default parameters, Proxy objects, and the Reflect API.

Release 4.9 also makes block level constructs such as class and let available outside of strict mode and adds support for the sticky flag on regular expressions and customizable Object.prototype.toString output.

Read more from the source: v8project.blogspot.com

Looking ahead: Microsoft Edge for developers in 2016

MS Edge priorities for 2016: better extension API, performance, more ES6 support, WOFF2, Web Notifications and more

 

We’ve been immersing ourselves in your feedback, reviewing development trends, and meeting with partners and developers around the globe to inform where we take EdgeHTML next. We want to ensure we’re focusing on the most impactful work! In the spirit of continuing our opennness, we’d like to share our priorities for 2016.

Read more from the source: Microsoft Edge Dev Blog