HTTP/2 largely won't help the problems mentioned in the article. If I'm loading 200+ assets for 30-50 hosts, HTTP/2 can't help because I'm making 30-50 TCP connections and fetching 5-8 resources over each. The efficiency of HTTP/2 over HTTP/1.1 really doesn't excel when fetching so few resources per connection.
HTTP/2 helps when you are downloading 200+ assets for 1 or 2 hosts.
I routinely use HTTP/1.1 pipelining from the command line to retrieve 100 assets at a time. But these are assets that I actually want: i.e., the content.
Somehow I doubt that the 200+ "assets" coming from 1 or 2 hosts automatically when using a web browser authored by a corporation or "non-profit organization" that is connected to the ad sales business are going to be "assets" that I actually want.
HTTP/2 helps when you are downloading 200+ assets for 1 or 2 hosts.