I might break my "no beta-testing unless paid" rule for this. I am beyond ready for quic-ness.👍🏻

https://twitter.com/JustinKotalik/...

I had no idea HTTP/3 even existed.

I've only seen one http/2 implementation in a work project before. 🙄

@Root
Most of my projects support it in the last year, but not many of my consumers are aware.

HTTP/3 is good for clients and they MAY notice a small difference on a slow connection provided they have a similar site over http/2 or http/1 to compare it to. Meanwhile, it increases server usage, making the general case slower.

Furthermore, http/3 is just http/2 over a different network protocol: the http protocol hadn't changed unlike the difference between http/1 and http/2, which is heavily asynchronous and stream based compared to it's predecessor.

Why would you break your beta policy for this?

@AlgoRythm
That's not actually a question 😉

@SortOfTested wondering what got you excited about http/3 when http/2 is a much larger change?

@AlgoRythm
Missed this. A: It's the whole package. Edge-capable web servers with ease of use that stay bleeding-edge current are a bit of a unicorn. I appreciate not only their work, but how far ahead of the game they manage to stay.