QUIC is more than a replacement for TCP
enz
12 points
5 comments
June 22, 2026
Related Discussions
Found 5 related stories in 100.8ms across 11,301 title embeddings via pgvector HNSW
- Noq: n0's new QUIC implementation in Rust od0 · 179 pts · March 19, 2026 · 59% similar
- QUIC has a lot going for it, but it is a large library (six figure LoC) tosh · 19 pts · May 19, 2026 · 59% similar
- Quad9 Enables DNS over HTTP/3 and DNS over QUIC itchingsphynx · 54 pts · April 02, 2026 · 56% similar
- When "idle" isn't idle: how a Linux kernel optimization became a QUIC bug sbulaev · 61 pts · May 12, 2026 · 55% similar
- Show HN: HTTP/3 and raw QUIC client/server APIs for Node.js brian_meek · 13 pts · June 08, 2026 · 52% similar
Discussion Highlights (2 comments)
qubex
Yeah I keep thinking that Reticulum & QUIC are the TCP/IP of the future.
GL26
QUIC will be more than a replacement for TCP once we will have broken the speed boundary that allows a distant server to control a robot (which requires quick reaction speeds to correct for instability time constants). For now, everyone is forced to embark their decision algorithms on Jetson Nanos to control robots, which makes prices quite high, in a certain future where time frames will be optimized, we can see "Robotic controlling as a service" platforms, that will make the price of robots drop by a significant ammount