> Imagine if we had that same attitude with regards to HTTP. Well, many do. You wouldn't believe the number of broken HTTP clients/servers out there. The diff

> Imagine if we had that same attitude with regards to HTTP. Well, many do. You wouldn't believe the number of broken HTTP clients/servers out there. The difference is that most HTTP clients/servers have to work with some significant subset of the pre-existing HTTP infrastructure (otherwise why would anyone use them?) and so that constrains their implementation to be "mostly correct". It's literally network effects :). Libraries on the other hand usually start out with a single consumer and have no such constraints on their implementation so you end up with various levels of ossified brokenness or breaking non-ossification.