UDP is a protocol, not an API
replyTrue. But it’s also true that trying to shoehorn every use case into TCP streams is counter productive.
replyA stream API can layer over UDP as well (reading in order of arrival with packet level framing), but such a stream would a bit weird and incompatible with many stream consumers (e.g. [de]compression). A UDP API is simpler and more naturally event (packet) oriented. The concepts don’t mix well.
Still, it would be nice if they browser supported a UDP API instead of the weird and heavy DTLS and QUIC immitations.
TCP or UDP are orthogonal to this, so the original comment feels like a non sequitur. These streams are not network streams and could be a file, chunks of procedural audio, or whatever.
replyThe browser does have a UDP data stream available for applications to send arbitrary bytes over UDP; it's part of WebRTC.
replyWe're too busy building products while waiting for the perfect system to arrive.
replyI’m building everything from first principles, I’m not climbing the exponential curve with some billionaire that has to finance it.
replyI really doubt you are. you're not visiting the transistor shop every time you want to build a react component
replyGood thing your confidence is a soft requirement :)
reply