Look ma, HTTP/2!

And it's retarded!

I might rant about HTTP/2 sooner or later. It's a backwards-compatibility-breaking protocol that really doesn't do shit.

What happened?

are you comparing express v http2?

@AlgoRythm it improves performance quite a bit.

Especially on sites with many extra resources, for simple pages, not so much.

@Voxera The performance boost is really only noticeable in certain situations... and you can achieve the same performance with http/1 with a little bit of a custom connection. It's really not worth breaking backwards compatibility over, whatsoever.

I mean you could just allow both HTTP2 and HTTP anyway

@AlgoRythm sometimes you have to break things to move forward.

Also the goal AFAIK is to have a high-level compatibility with HTTP.

@Cultist But is is a move forwards?

@AlgoRythm Definetely! HTTP/1.1 is a dinosaur. It's made for a static web.

We tried to improve our old messenger, with pipelining... but that didn't work well.

It won't solve all our problems but it's a good step forward imho.

Soon http3 will start rolling out where tcp is replaced with a udp like protocol called quik to further improve performance.

https://en.m.wikipedia.org/wiki/...

This will give webpages the same possible response time as games, sub 50 milliseconds for small requests.

@Voxera https://tools.ietf.org/html/...

@Voxera wow. thanks for the heads up!

This got a _very_ stupid laugh out of me.

@Voxera google uses it quite a while

https://github.com/GoogleChromeLabs...
static http2 server

@Voxera That is neat. I don't think http/2 is near. It still runs TCP and the only change is streams. Not enough good for me to abandon all of my websockets