3 ms·
> your language should be participating in the future of HTTP Nah. It's fine to leave any networking to external libraries.
by floatboth 6y ago
> your language should be participating in the future of HTTP
Nah. It's fine to leave any networking to external libraries.
- rektide 6y agoIf you had clicked the link, you'd see that it is primary a list of libraries. Admittedly I had not considered that Swift can use native C libraries. I'm not sure whether it makes sense to expect a wrapper library or not, whether that would help. But overall, I'm pretty sure no one is doing nor advancing towards HTTP3 in Swift at the moment, which makes me feel like the Swift community is not a serious player for general development. Some trivia, not necessarily a recommendation: Node.js is the only language I know of working towards HTTP3 support in the platform (also in this link, evidence that I may be biased in my priorities): https://github.com/nodejs/node/issues/23064 https://github.com/nodejs/node/issues/23064