3 ms·
HTTP2 and HTTP3 themselves are relatively recent and widely used. They also happen to work on top of TCP and UDP rather than supplanting them. ACME protocol is
by cestith 4y ago
HTTP2 and HTTP3 themselves are relatively recent and widely used. They also happen to work on top of TCP and UDP rather than supplanting them.
ACME protocol is fairly recent and widely used.
WebSocket protocol is barely over one decade old.
DNSSEC is a little over a decade and a half old.
NVMe over Ethernet is barely half a decade old and still gaining support.
400GBASE-LR4-6 is from last year. People are still working on terabit/second Ethernet.
There are loads of protocols on top of the HTTP family. DNS over HTTP is a protocol. SOAP, JSON-RPC, and REST are protocols. IPFS is a protocol.
To say there's no innovation in protocols when it's literally happening all the way up and down the stack is just silly and shortsighted.
- icedchai 4y agoOk, you have a point. There is innovation in the "infrastructure" space for protocols. Almost none of the stuff you describe is directly visible to end users. I should've said there's no new application protocols, like SMTP, POP, XMPP, SSH, etc. Example: I had hopes there would be some sort of federated "instant messaging" standard so we wouldn't all need to use separate apps.