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

SPDY may be technically sound but...

Mozilla Corp: Wholly 0wned Subsidiary of Google Inc




Why? AFAICS, SPDY is open and available for everyone who wants to implement it.

What's so bad about companies making it open, free and open source, thus contributing to a better Internet experience for everyone? No one limited SPDY to Google sites - Microsoft and Yahoo are free to implement it for their servers and enjoy browsing speedups with Chrome and (soon) Firefox 11.


So will my web server handle HTTP 1.1, SPDY, and HTTP Next then?

Is Mozilla acting in the interest of the Open Web or was this a bargaining chip with their $300M default search provider deal?


Yes. Apache already has mod_spdy and nginx has plans to implement it. Browsers fallback to regular http if the server doesn't speak spdy. There are no disadvantages for you.


SPDY may be technically sound but...

Traffic is harder to debug. Google continues to act like it owns the Web.

These are disadvantages for the world.

Bring on the downvotes of the naive Googlers! This place was getting boring anyway...


I think programmers have achieved harder tasks than detecting which protocol the server speaks and speaking its language, starting with the most optimal protocol and falling back to simpler and more common ones.


Mozilla refused to implement NaCl and WebP; it looks like they're evaluating Chrome features on a case-by-case basis.


Perhaps it does look like that. It also looks like Mozilla has a healthy incentive to shadow Google in the form of their recent search deal.

Is Mozilla doing the best thing for the Web or further cementing the current browser landscape? Will it be better when I have to write my crawlers to work with HTTP 1.1, SPDY, and HTTP Next?


You don't have to write your crawlers to even work with HTTP 1.1; all the web servers out there will respond just fine to HTTP 1.0 requests, even through HTTP 1.1 is ubiquitous and has been in use for over a decade now. What makes you think that SPDY-enabled web servers won't be compatible with HTTP?


SPDY may be technically sound but...

My objection to this turn of events is almost entirely related to the behavior of Google and their search deal with Mozilla. Mozilla has compromised their principles again and again for Google and it is accelerating.

I'm tired of Google's doublespeak and lies about "Open Web" and open standards. If SPDY takes off, we will all have to think about supporting it and if it's built correctly that will be fine. I seriously have my doubts.

It would have been much less suspicious if the second browser to adopt SPDY was Safari or IE. Right now, it looks like Google is essentially bribing an "independent" browser vendor to implement their half-baked standards so they can turn around and claim "it's a web standard!".

It's like 1999 but now with corporate protectorates!


What makes you think you have to do anything? If spdy takes off all you have to do is upgrading your http library to advantage of it. Besides the servers still speak http so your crawlers will keep working even if you don't upgrade.


SPDY requires an explicit upgrade of the connection.




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

Search: