@lunareclipse http/3 breaks correct layering (shoving implementation bits where they don't belong) and reimplements on udp what tcp has been designed for in the first place, http/2 has design flaws (its multiplexing design is fundamentally misguided) that resulted in http/3 appearing so quickly after everybody had just deployed it (and cursed stuff like server push), and http/1 is legacy jankfest