HTTP/2 explained
This is a "living document" in the sense that I keep posting updates, and I care about and value feedback, questions and comments I get about it. This document improves over time thanks to a joint effort.http://daniel.haxx.se/http2/
How much difference does HTTP/2's server side push make?
The DOM and all additional resources don't need to be parsed, the client can already begin the download of the `screen.css` resource, without "wasting time" processing the DOM and all external resources, only to make a new request to the server to begin fetching them.http://ma.ttias.be/service-side-push-http2-nghttp2/When you add this all up for all resources on a page, this can easily save 100-200ms of the total page load/paint of a website. Those are numbers that should really have you consider implementing HTTP/2.
Join 9,500+ smart developers
Get my monthly newsletter with what I learn from running Spatie, building Oh Dear, and maintaining 300+ open source packages. Practical takes on Laravel, PHP, and AI that you can actually use.
No spam. Unsubscribe anytime. You can also follow me on X.
"Freek publishes a super resourceful and practical newsletter. A must for anyone in the Laravel space"
Goodbye SPDY
Chrome has supported SPDY since Chrome 6, but since most of the benefits are present in HTTP/2, it’s time to say goodbye. We plan to remove support for SPDY in early 2016, and to also remove support for the TLS extension named NPN in favor of ALPN in Chrome at the same time. Server developers are strongly encouraged to move to HTTP/2 and ALPN.http://blog.chromium.org/2015/02/hello-http2-goodbye-spdy-http-is_9.html
Five reasons why the shut-op operator should be avoided
An old, but still relevant, blogpost by Derick Rethans (of Xdebug fame) about why the @-operator should be avoided.
http://derickrethans.nl/five-reasons-why-the-shutop-operator-should-be-avoided.html
The Zend Framework 3 roadmap
Zend Framework 3 will be an evolution from ZF2, concentrating on simplicity, reusability, and performance.http://framework.zend.com/blog/announcing-the-zend-framework-3-roadmap.html
Optimizing for PHP7, and supporting PHP 5.5 seems like a good idea.
StackExchange's Performance Dashboard
An overview of the hard- and software used by the StackExchange network to render 560 million pages views per month.
Architecting Websites For The HTTP/2 Era
The arrival of HTTP/2 will require a bit of re-thinking how we handle websites (and webservers), so perhaps it's time to reflect on what those changes can bring. This post is based entirely on theory (the HTTP2 spec), as HTTP/2 is hard to test today (with a lack of servers and browser support).https://ma.ttias.be/architecting-websites-http2-era/
Performance profiling with the Chrome Dev Tools
Patrick Dubroy explains how you can track down client-side performance problems using the Chrome Dev Tools.
http://vimeo.com/77322983
The best 6TB hard drives according to Backblaze
Backblaze is transitioning from using 4 TB hard drives to 6 TB hard drives in the Storage Pods we will be deploying over the coming months. With over 10,000 hard drives needing to be purchased over the next several months, the choice of which 6TB hard drive to use is critical.https://www.backblaze.com/blog/6-tb-hard-drive-face-off/
Backblaze needs to store 130 TB of incoming customer data every day.
Nginx HTTP server boilerplate configs
Nginx Server Configs is a collection of configuration snippets that can help your server improve the web site's performance and security, while also ensuring that resources are served with the correct content-type and are accessible, if needed, even cross-domain.https://github.com/h5bp/server-configs-nginx
SPDY is speedy
Compare load times of the unsecure HTTP and encrypted HTTPS versions of this page.https://www.httpvshttps.com/
Inside Composer's speed boost
If you've been following the news, you'll have noticed that yesterday Composer got a bit of a speed boost. And by "bit of a speed boost", we're talking between 50% and 90% reduction in runtime depending on the complexity of the dependencies. But how did the fix work? And should you make the same sort of change to your projects? For those of you who want the TL/DR answer: the answer is no you shouldn't.http://blog.ircmaxell.com/2014/12/what-about-garbage.html
HTTPS Everywhere
When creating a new website you should always use HTTPS. Here's a video recorded at Google I/O earlier this year on the why and how.
The New York Times switched to HTTPS last month. Here are their reasons for doing so:
Perfmap
Perfmap consists of a bookmarklet and Chrome extension to create a front-end performance heatmap of resources loaded in the browser using the Resource Timing API.
PHP 7 moves full speed ahead
Spoiler: it's all about performance. Coming to a host near you in 2015.
http://www.infoworld.com/article/2841561/php/php-7-moves-full-speed-ahead.html
Best Practices for Using the Vary Header
Vary is one of the most powerful HTTP response headers. Used correctly, it can do wonderful things. Unfortunately, this header is frequently used incorrectly, which can lead to abysmal hit ratios. Worse still, if it's not used when it should be, the wrong content could be delivered.http://www.fastly.com/blog/best-practices-for-using-the-vary-header/
