Hopefully we all agree that maintainability is the most important quality of code (after successfully performing the feature that it was meant to implement.) Wr

Hopefully we all agree that maintainability is the most important quality of code (after successfully performing the feature that it was meant to implement.) Writing readable, modular code is key to getting the most out of developer time and preventing bugs. With that in mind HTTP/2 is a huge step backwards. And for what? Slightly faster speeds? This is a non-problem. When I see a slow site and view the network performance to discover why (using tools that would most likely not work under HTTP/2) here is what I inevitably see: * Massive video and JavaScript for ads * JavaScript tracking code * Massive HTTP headers with unnecessary cookies * Unnecessary, bloated JavaScript libraries * Unnecessary, bloated CSS files * Gratuitous unoptimized images * No attempt at optimizing HTTP caching settings * No attempt at HTTP compression (gzip) These will still be the main bottlenecks with HTTP/2. HTTP/2 solves no problem and makes network application development more difficult by making the network calls opaque and gratuitously complex.