@FritzAdalis "It depends", QUIC's (simplified) origin story is that a bunch of large co's were having the performance of their websites held back by TCP and Windows/Linux/Darwin's kernel implementations, so they made their own TCP running over UDP (to force everything into user space, for full control).

The idea to have kernel QUIC is funny in this context because it's "final" step of moving everything back to what it was like before

@wolf480pl @FritzAdalis Sorta, I would say that SCTP is a exceptionally different transport compared to everything else, so it's not what I would compare anything with (and I say this as a reasonably heavy SCTP user for bgp.tools)

QUIC is basically a everything feature transport at this point, and given that was the point originally (aka, innovating beyond TCP) it makes sense ! The only problem is what supports what in server/client etc. There is defo a universe where QUIC could/should have just stayed as the Google transport protocol rather than standardisation, as modern day QUIC still has considerable drawbacks, I suspect most people do not see a huge impact in it's implementation in most cases