Earlier quoted context omitted.
Rust so far does not cover all architectures that C can reach. When the GCC implementation is ready, it might change, but not yet.
What sort of architecture are you envisioning where you'd need HTTP3 and Rust can't build for it? Once you get a microcontroller fast enough to handle Http3, you are talking about well known platforms (such as ARM, MIPS, x86). All of which are supported by Rust and LLVM. https://doc.rust-lang.org/nightly/rustc/platform-support.htm...
LiteSpeed QUIC (LSQUIC) is an open-source implementation of QUIC and HTTP/3
41–44 of 44 posts
Re: LiteSpeed QUIC (LSQUIC) is an open-source implementation of QUIC and HTTP/3
#42Earlier quoted context omitted.
What sort of architecture are you envisioning where you'd need HTTP3 and Rust can't build for it? Once you get a microcontroller fast enough to handle Http3, you are talking about well known platforms (such as ARM, MIPS, x86). All of which are supported by Rust and LLVM. https://doc.rust-lang.org/nightly/rustc/platform-support.htm...
Keeping in mind that I needed to write code against node 0.13 because it was the last version of node supporting floating point emulation when there is no hardware fpu, I was surprised to learn what kind of trash is out there running the internet. There is list of supported architectures of the software in question and though I don't remember it in details, I'm sure that there were items in it that I couldn't find in…
I'm fairly confident in saying any place you can run any node version, you can run rust.
Re: LiteSpeed QUIC (LSQUIC) is an open-source implementation of QUIC and HTTP/3
#43Earlier quoted context omitted.
TCP HOLB is hardly diminishing returns; it’s the defining way in which HTTP/2 is not uniformly superior to HTTP/1.1—because of it, for a meaningful fraction of users, single-connection HTTP/2 behaves visibly worse than its primary competition, up-to-six-connection HTTP/1.1. (Lack of WebSockets support used to be another point, but that got fixed a year or two back.) Some of the other benefits of HTTP/3 over HTTP/2, l…
HTTP2 always seemed like a great idea for the backend and a "meh" idea for the front end. On backend systems where networks and lines are mostly reliable and fast, HOLB is generally not a problem. It's only when you start talking about connections outside a backend network that HTTP2's weaknesses start to show (specifically mobile networks).
Re: LiteSpeed QUIC (LSQUIC) is an open-source implementation of QUIC and HTTP/3
#44Earlier quoted context omitted.
Keeping in mind that I needed to write code against node 0.13 because it was the last version of node supporting floating point emulation when there is no hardware fpu, I was surprised to learn what kind of trash is out there running the internet. There is list of supported architectures of the software in question and though I don't remember it in details, I'm sure that there were items in it that I couldn't find in…
:) sounds like bcm4709. Funnily, rust wouldn't have a problem there, that's specifically a node problem because their JIT doesn't handle software FPUs. LLVM does. I'm fairly confident in saying any place you can run any node version, you can run rust. https://github.com/nxhack/openwrt-node-packages/issues/15