原文
| ||||||||||
| ||||||||||
![]() |
原始链接: https://news.ycombinator.com/item?id=43360251
Hacker News 上关于 HTTP/3 的讨论总结如下: 原文指出尽管 HTTP/3 已经广泛存在,但其采用速度缓慢。虽然 .NET 提供了不错的支持,但 Node.js、Go、Rust、Python 和 Ruby 等主要语言的标准库中都缺乏对它的支持。 讨论中的用户指出了实际的挑战和有限的益处。一些人质疑 HTTP/3 在 CDN 和负载均衡器背后的服务器到服务器流量中的价值。另一些人则提到,由于需要支持旧系统而导致在分发库时使用较新版本的 cURL 受到限制。还有一种观点认为,对于小型网站来说,HTTP/3 带来的性能提升可能无法证明其实施工作是合理的。一些人发现 HTTP/1.1 对于某些特定用例(如双向 Comet 流)已经足够。总体而言,人们普遍认为 HTTP/3 对于专注于功能开发和错误修复的团队来说优先级较低,尤其是在库支持不成熟的情况下。
| ||||||||||
| ||||||||||
![]() |
Support for Windows, Linux[1], and Mac[2] (the latter two with some caveats).
Overall, I think for most dev teams that are not building networking focused products/platforms, HTTP/3 is probably way down the stack of optimizations and things that they want to think about, especially if the libraries available have edge cases and are too early for production. Who wants to debug issues with low-level protocol implementations when there are features to ship, releases to stabilize, and defects to fix?
[0] https://learn.microsoft.com/en-us/dotnet/fundamentals/networ...
[1] https://learn.microsoft.com/en-us/dotnet/fundamentals/networ...
[2] https://learn.microsoft.com/en-us/dotnet/fundamentals/networ...
reply