> I could be wrong, but I see the HTTP/2 ploy as a proposed way to deliver more cruft, faster. Could not possibly agree more. I tried my own HTTP/1 site in tha

> I could be wrong, but I see the HTTP/2 ploy as a proposed way to deliver more cruft, faster. Could not possibly agree more. I tried my own HTTP/1 site in that site-tester, and it has a 105ms response time for entire pages. And my pages are dynamically generated. HTTP/2 (and especially the Mozilla/Google-imposed TLS requirement) takes away the simplicity of the web. The thing that allowed you to write a few lines of code, and suddenly your old Commodore 64 was a web server. Increased complexity is going to lead to more and more of a monoculture, which is going to leave us all more vulnerable to attacks (like with OpenSSL and Wordpress.) The article is also a little bit ironic for me. He speaks of unnecessary widgets added to pages, yet his unnecessary sidebar is overlapping the text in the article, cutting off the ends of every line, and even maximizing the window doesn't get rid of it ( picture: http://i.imgur.com/qJeyP5v.png http://i.imgur.com/qJeyP5v.png ). I had to use "inspect element" to delete the sidebar to read the page in full. (I'm sure it doesn't happen for everyone or it'd have been fixed, but it does on my browser.)