Get over my connection. Some places it's quite common.

The thing is you are both missing the point:

The tech landscape is growing increasingly complex. We shouldn't be adding more obstacles to getting involved than we already have.

That's how horrible Legacy-things get built. We don't need to do that to our internet.

It's only a barrier to entry if you insist on using http 2.0 which is a CHOICE you make. Don't use http 2.0, just like you can choose to use your internet connection for whatever.

But according to this discussion over at reddit, HTTP 2 seems to be made required for "real" sites:

http://www.reddit.com/r/technology/comments/1qj1tz/http_20_t...

So now it's NO choice after all. If you want to run a "real" site, not only must you pay rent for your DNS, you are now also being extorted into paying money to CAs. CAs which can be subverted by the NSA, so they're effectively worthless anyway.

That's a bad move. Internet should be getting cheaper, not more expensive.

This whole HTTP 2.0 affair is turning into a real piece of extremely short-sighted shenanigans. Given W3C's green-light on DRM in HTML, we should start questioning if we want to entrust them with these sort of tasks in the future. They have gone completely off the rails.

You misunderstood. Nobody forces you to use HTTP 2.0, you can use HTTP 1.1 or even 1.0.

And, again, HTTP 2.0 has nothing to do with CA prices.

>You have 10mbps connection! At your home! How much do you pay for it?

I hope you understand it's mbit. If so, I've got 50mbps over here and I pay €50 (that's about $67 USD) per month, which includes 50 TV channels and interactive TV (I'm Dutch, I hope I described it correctly)

The situation (s)he describes is fairly common; I've got a Raspberry Pi and an old laptop running as servers over here, on which I do experiments and host small websites. They've got StartSSL certs, which suck, but they do their job at least. If you put enough effort in the process and not just blindly fill in the forms, you'll get there.

So, it's not a problem for you to use TLS with HTTP 1.1? What's the problem with HTTP 2.0 then?