Hacker News new | past | comments | ask | show | jobs | submit login

Don't confuse the cart and the horse. The IETF standardization process has never been less relevant than it is today. The reality of deployment of a "next-generation HTTP" involves two things, neither of which the IETF has any say in: (a) whether anyone can improve HTTP as it runs between a mainstream browser (or some as-yet unforeseen browser replacement) and a content serving backend in a way meaningful enough to drive adoption, and (b) buy-in from the major browser owners.

That's the way it's supposed to work; the horse is meant to drag the cart. The RFC database is littered with cart-led insurgencies that went nowhere. If binary HTTP is one of those, it'll join them as a historical curiosity.




My fear is that now that Google controls a significant part of HTTP traffic, plus the client side of the story (Chrome + Android), it is in a condition to force things in one way or the other...


I suppose that's a valid concern, but note that Google's control over the protocol was already pretty strong by dint of running Google.


Do you think Google is now in a better position to force things in one way or another than Microsoft was in the 90s?


It's in a similar position. And see how that ended up with Microsoft — we're still suffering the consequences.


You mean like how virtually all of consumer software development now happens either on the web or on a platform that didn't exist until 2007?


I'm actually kind of OK with XMLHttpRequest.


I am quite sure Microsoft views it as huge mistake on their part. :)




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: