The first one requires money be spent on every site.
The second one requires that the feature be maintained in major web servers. Which it will be. On a per-site basis, the developer needs to do nothing.
The second one requires that the feature be maintained in major web servers. Which it will be. On a per-site basis, the developer needs to do nothing.
Lots of things need to happen for HTTP/2 to 'stay alive'.
Your use of the future tense does not convince me.
It's built into the software because enough sites will still be using it fifty years from now, even if it's a minority of traffic.
I seriously doubt you'll ever see TCP blocked.