The perils of federated protocols

Posted May 19, 2016 6:06 UTC (Thu) by roc (subscriber, #30627)
In reply to: The perils of federated protocols by josh
Parent article: The perils of federated protocols

Quite so.

Marlinspike carefully phrased his mention of HTTP to dance around the fact that HTTP/2 is being deployed right now (and experimental predecessors have been deployed for years). That section of his post is deliberately misleading.

He's right that decentralized evolution imposes costs, including delays. But he's not right that centralized always wins.

The perils of federated protocols

Posted May 19, 2016 11:58 UTC (Thu) by khim (subscriber, #9252) [Link] (2 responses)

It's a bit dishonest, but not by much. By your own admission: HTTP/2 is being deployed right now and experimental predecessors have been deployed for years.

Basically it's shows that federated world could be moved along — if you are willing to spend about 10x more resources and accept about ⅒ of development speed.

The perils of federated protocols

Posted May 19, 2016 12:47 UTC (Thu) by hkario (subscriber, #94864) [Link] (1 responses)

we already had a web with just one client that actually worked: IE6

did we learn nothing?

The perils of federated protocols

Posted May 19, 2016 17:11 UTC (Thu) by khim (subscriber, #9252) [Link]

did we learn nothing?

Sure. The lesson is obvious: no matter how dominant is your platform if you stay dormant for years sooner or later someone will bypass you.

The web which we enjoy today is result of Microsoft's attempt to rebuild it today: architecture astronauts have won and instead of quickly adding features to MS IE which would make a breakout attempt impossible Microsoft decided to rebuild everything from scratch

The end result was something years later, with reduced functionality and insane resource consumption.

This gave chance to the Firefox/Safari/Chrome—but also gave developers of these monsters a false sense of security: they decided that since Microsoft was stupid all other contenders for the “try before you buy” app deployment platform will be just as stupid. The height of folly is, of course, stillborn Firefox OS but I think that the ball was lost when Mozilla decided that it could afford to dictate the rules to app developers: “it's my way or the highway”… most developers have chosen the highway… well some have picked some other highway, but almost everyone left anyway…

Some still believe that they will return, but I seriously doubt it: Apple and Google are not like Microsoft (at least not yet), they iterate fast and already made web development mostly irrelevant. I fully expect to see regression of web platform in the next few years—it'll be interesting to see how this process will look like.