Refactoring development

Ramblings from the trenches...

View on GitHub
We’ve moved on from Prestel (RFC1149) to HTTP/1.0,  HTTP/1.1 and finally moved to HTTP/2.

This is the biggest step-change since moving off RFC1149. In a nutshell,

We all know before we should start using something we should wait till version 3. - I think we’ll make an exception in this case!


 

Now we just need to wait till everyone’s favorite webserver (Nginx) supports HTTP2 (currently it supports HTTP2’s prototype: SPDY 3.1).

It will also be interesting to see how Google’s PageSpeed Module adapts to HTTP2 as quite a few of the inlining optimisations are no longer required.


 

Post-HTTP

Given HTTP has been around for 20+ years now, it’s done very well to bootstrap the world into using common agreed interchange formats (mainly by keeping things very simple).

In the next 20 years we’re likely to see the rise of the decentralised internet, one depending much more heavily on peer-to-peer for caching at the edge. One such effort is IPFS which is taking the GIT-like content addressable direction (I.e. a file’s key is its hash). | | Almost all project management focuses on one project rather than the n competing projects. I understand at this larger level it’s called ‘program management’.  http://www.artofmanliness.com/2013/12/03/beyond-sissy-resilience-on-becoming-antifragile/