4 ms·
> Therein lies the problem. Do we really all have to shoulder youtube's (and porn networks) problems? No, you don't. Whether you're working on the client or se
by mwcampbell 6y ago
> Therein lies the problem. Do we really all have to shoulder youtube's (and porn networks) problems?
No, you don't. Whether you're working on the client or server side, you can keep using HTTP/1.1, and the other side will downgrade to accommodate you. Meanwhile, those of us who want to optimally serve our users on both good and bad connections will just use the multiple, freely available implementations of HTTP/2 and eventually HTTP/3.
- varjag 6y agoThis is half truth at best. It's only a matter of time until HTTP/1.1 is forced out by the tech/browser oligopoly: just look where we are with plaintext HTTP now. The reason for HTTP3 is marginal gains that only make sense at enormous scales for large operators. The rest of us pay for this with increased complexity.
- mwcampbell 6y ago> just look where we are with plaintext HTTP now. Yes, and the upgrade to HTTPS has been an improvement for end-users.
- varjag 6y agoAnd upgrade to HTTP3 is going to be even bigger improvement! Except when you don't need it, but are stuck with obsolete ecosystem otherwise.
- tannhaeuser 6y agoFortunately, there is Cloudflare (incidently, also behind the http/3 push) who'll be happy to proxy your old site using http/3