45 ms·
I think you are missing a lot of context regarding what SPDY is, was and it's relation to HTTP/2[1]. In short, SPDY was an experiment designed to test some pro
by kbenson 11y ago
I think you are missing a lot of context regarding what SPDY is, was and it's relation to HTTP/2[1]. In short, SPDY was an experiment designed to test some proposed strategies for future HTTP protocol development, which it did. It was adopted as a starting point for HTTP/2. After HTTP/2 was released, Google announced it would eventually be phasing out SPDY. This is a good thing.
> It's certainly true that HTTP/1.1 isn't perfect and there are practical ways it could be improved, but I don't think this presentation makes a strong case for adopting HTTP/2 as the way forward.
Well, I read it more as a "If you are planning to use HTTP/2, here are ways in which you might want to alter how you plan out your service", not "You should use HTTP/2, now here's the stuff you need to go change so you can do so." Alternatively it can see it as "here's the performance hacks you no longer have to do with HTTP/2 because it has good mechanisms for this built in." In any case, I didn't get a strong vibe about how we need to abandon HTTP 1.1.
1: http://en.wikipedia.org/wiki/HTTP/2#Genesis_in_and_later_differences_from_SPDY http://en.wikipedia.org/wiki/HTTP/2#Genesis_in_and_later_dif...
- Silhouette 11y agoIn short, SPDY was an experiment designed to test some proposed strategies for future HTTP protocol development, which it did. That may always have been the intent, but I'm not sure that was clear to those outside the Google bubble. For example, there were numerous articles and blog posts and conference talks around the time that SPDY became a serious proposition with a similar tone to the HTTP/2 commentary we are seeing today. No doubt there were exceptions, but much of that advocacy didn't exactly come with "big red box on the first slide" warnings that SPDY was an experiment, and readers/viewers should only use it in production if they had the resources available to update things again in the relatively near future. I do appreciate that the big news for HTTP/2 is that it has reached a more formal level of standardisation, but in the modern Web industry when browsers do whatever they want every six weeks anyway, that isn't worth as much as it used to be. Even today, there are few production-grade tools around that actually support HTTP/2 in anything close to its final form, including a lot of the projects that do support SPDY. Phasing out browser-side support for the latter as soon as early 2016 seems like a typically aggressive Google drive to shift the web to a new technology it favours, at the expense of forcing everyone to adjust/upgrade their existing working deployments. I'm very uncomfortable about how readily they are willing to do that in their browser these days, but I don't think the permanent-beta mentality has any place in server/network infrastructure at all.