3 ms·

> I have 10mbps upstream connection. I have a Raspberry pi and a Linux-powered NAS. that means you pay for your internet connection and for the hardware you ru

by pilif 13y ago

> I have 10mbps upstream connection. I have a Raspberry pi and a Linux-powered NAS. that means you pay for your internet connection and for the hardware you run the website on. Why is also paying for a certificate a problem? I get the hobbyists approach, but especially for hobbyists I think it's better to stay with HTTP/1.1 which, as a plain text protocol is a lot easier to learn than the complicated ugly mess of HTTP/2.0. Also because of the SSL requirement, development will probably never happen over HTTP/2.0 - or do you want to create or even purchase new certificates for all your development projects? A HTTP/1.1 server is something normal people can implement. A HTTP/2.0 server is something for others to implement and a pain to debug. I see HTTP/2.0 as a new transport protocol to transmit what we know as HTTP/1.1. None of the request/response semantics has changed between 1.1 and 2.0 (minus server push, but if you want to support older clients, you'd have to use other techniques anyways). If you're just running your own little page, nothing is stopping you from using HTTP/1.1. Once your site is big enough to actually benefit significantly from HTTP/2.0, you will have the money for a certificate. It's the latency for your clients you can shrink with 2.0, but you'd get bigger benefits from moving off hosting on a cable modem than by moving to 2.0. At that point, you'll have other, bigger costs to pay than the certificate.

rakoo 13y ago
> that means you pay for your internet connection and for the hardware you run the website on. Why is also paying for a certificate a problem? Because the internet access and the hardware would have been bought regardless of the activity, for other purposes. (S)he was already paying for it, and used it for other purposes. Running a web site _happens_ to be one of its use, but is not the one goal. The fact that it is free to run a web site means that I can run my website on my laptop. On the other hand, the certificate would have to be bought _only_ for this, because it is its only use: be able to play the HTTP/2.0 game.
parasubvert 13y ago
TCP stacks long ago became something for other people to implement and hard to debug. Same with most encryption. There will always be a hobbiest path with http/1 but the biggest sites in the world are building http/2 for their use cases. The internet is no longer predominantly a hobbiests' playground and hasn't been in some time. Mainstream success leads to this sort of transformation by definition.

by pilif 13y ago

rakoo 13y ago

> that means you pay for your internet connection and for the hardware you run the website on. Why is also paying for a certificate a problem? Because the internet access and the hardware would have been bought regardless of the activity, for other purposes. (S)he was already paying for it, and used it for other purposes. Running a web site _happens_ to be one of its use, but is not the one goal. The fact that it is free to run a web site means that I can run my website on my laptop. On the other hand, the certificate would have to be bought _only_ for this, because it is its only use: be able to play the HTTP/2.0 game.

parasubvert 13y ago

TCP stacks long ago became something for other people to implement and hard to debug. Same with most encryption. There will always be a hobbiest path with http/1 but the biggest sites in the world are building http/2 for their use cases. The internet is no longer predominantly a hobbiests' playground and hasn't been in some time. Mainstream success leads to this sort of transformation by definition.