Lee M

Thanks for the technical explanation! I'm glad a lot of thought went into this. Diving a bit deeper, I'm seeing a lot of the work is actually coming from `debugOnly`...

It's a shame NIO isn't better resourced, as an Apple project 😔 Would love to see QUIC transport implemented - there are maturing implementations now in C, C++, Java, Go,...

I think there's an important distinction between QUIC, which is the underlying UDP transport, and HTTP/3, which sits on top of QUIC. QUIC became a standard over a year ago...

I think by far the easiest way of implementing this would be just to borrow some of the work done with Netty and Quic here: https://github.com/netty/netty-incubator-codec-quic swift-nio is loosely based...

@Lukasa - is there any update on what the thinking is on this internally? QUIC is long standardised now and supported in all browsers, with implementations in all major languages...

Appreciate the quick, clear response. Sad that server-side swift isn't yet getting any investment in these modern standards, but fair.

Ladybug looks great btw 👍 Got a few projects lined up for this

This would be very useful

@jshier - is there any intent on getting this in at all, or are these commits for your own fork/personal use?

This repo seems to be undergoing active development: https://github.com/swift-quic/swift-quic Thanks to @kennethlaskoski and @btoms20 for embarking on this effort 🎉 👏