6 ms·
I can only be suspicious about too much complexity and stacking in what is essentially infrastructure - that should be reliable, and therefore have minimum comp
by BlueTemplar 7y ago
I can only be suspicious about too much complexity and stacking in what is essentially infrastructure - that should be reliable, and therefore have minimum complexity. Any initial opportunity costs are tiny when these protocols are used by billions of devices !
- shadowgovt 7y agoBut they aren't. The vast majority of novel protocols never see a billion adopters. There are a handful that have; the email protocols are one, HTTP is another. Nobody's stopping anyone from building new protocols... Except, of course, the fact that nobody wants to adopt a new protocol. But if someone does come up with an indispensable alternative to HTTP(s), it should find traction, right?
- BlueTemplar 7y agoGoogle and Facebook were very glad to "adopt" XMPP : https://salibra.com/p/the-death-of-jabber-8ea395e82f5b https://salibra.com/p/the-death-of-jabber-8ea395e82f5b
- shadowgovt 7y agoXMPP is an excellent example of why existing flexible protocols push out novel protocols. When Google and Facebook wanted to improve the user experience of their XMPP clients, they encountered roadblocks in the fundamental design of the protocol itself. They finally reached a point where exiting the protocol was easier than improving it.
- BlueTemplar 7y ago"Exiting" doesn't seem to be the right word? How do we stop Google, who is currently "exiting" HTML ?
- shadowgovt 7y agoShould we? I thought you were making the argument that HTML was a bad fit for non-hyperTEXT content. From up-thread: "Why use the HyperTEXT Transfer Protocol for things completely unrelated to text..." If Google agrees with you, would we want to stop them?
- BlueTemplar 7y agoBy "exiting", I mean Embracing-Extending-Extinguishing.