We already have Server Sent Events over HTTP/1.1 so yes this was completely unneccessary. The TCP head-of-line problem makes HTTP/2 a solution ONLY for people

We already have Server Sent Events over HTTP/1.1 so yes this was completely unneccessary. The TCP head-of-line problem makes HTTP/2 a solution ONLY for people that abuse the bandwidth in the first place (read big centralized coorporations that have large bills of wasted eletricity) making it a non-solution across the board for the distributed (hosting HTTP from home) humanity. The reason for "eternal growth" mindset is job security: "What are all these people going to do now that we have the final HTTP/1.1 working perfectly across the globe on every machine?" Depreceate and "improve"... In my mind the second version (not always named 2) is always the final version, see half-life and starcraft for other stories that tell you a similar progression: you make 1.0 as well as you could and then take a pause and realize you need some final additions so 1.1 completes the product/protocol. (both HL and SC where rewritten in a large manner after they where "done"). 2.0 is often a waste of resources, see HL2+ and Starcraft 2, where the electricity prices are going now and for eternity you wont be able to play them anyway! Complexity has a price, HTTP/1.1 is simple!