4 ms·
> The alternative is that either browsers will be the only users of QUIC - or that each application is required to bring its own QUIC implementation embedded in
by Karrot_Kream 3y ago
> The alternative is that either browsers will be the only users of QUIC - or that each application is required to bring its own QUIC implementation embedded into the binary.
This is already being done with event loops (libuv) and HTTP frameworks. I don't see why this would be a huge issue. It's also a boon for security and keeping software up-to-date because it's a lot easier to patch userspace apps than it is to roll out a new kernel patch across multiple kernels and force everyone to upgrade.