3 ms·

I don't think you know what "proprietary" means, you don't pay Google to use SPDY. They solved a problem and made something better, case in point Facebook and

I don't think you know what "proprietary" means, you don't pay Google to use SPDY. They solved a problem and made something better, case in point Facebook and Twitter among others have already deployed it. If you do some research you'll find that most standards started as projects that came out of a single company or lab that were later adopted by industry.

threeseed 13y ago
No. You don't understand what proprietary means. SPDY is a trademarked technology owned by a private corporation. The only reason companies are adopting SPDY is because it is an improvement than HTTP. SPDY is far from perfect. The issue is that with core internet protocols this is not the way it should happen.
- AnthonyMouse 13y ago
  >The only reason companies are adopting SPDY is because it is an improvement than HTTP. I don't see the problem. >The issue is that with core internet protocols this is not the way it should happen. This is exactly how it does happen. Someone creates something, people like it, the creators don't enforce patents on it or try to keep it a secret, someone writes it up into an RFC. That's how internet standards are created. That's how they've been created as long as there has been an internet. Look at a counterexample. Microsoft with OOXML. Here we have a so-called standard which says things like "do this the way X version of Microsoft Word does it" without actually specifying how to do it. It's not an open standard, it's a document claiming to be an open standard on paper so that Microsoft can claim their proprietary file format is an open standard. No one else is expected to use it for any purpose other than attempting interoperability with Microsoft Office and Microsoft has no particular interest in having anyone even succeed in doing that. SPDY is not that. Google has published a reference implementation with source code. People other than Google use it for reasons having nothing to do with interoperability and Google services continue to be available to browsers without SPDY. "They didn't ask permission first" is just disingenuous griping -- who are they even supposed to have asked? SPDY isn't a problem. Hangouts are. I don't see source code for a reference implementation. I don't see anyone but Google implementing the protocol. That's how you know something is wrong.
  - zobzu 13y ago
    The point you're missing is that people don't use it because they think its good. They use it because they don't have a choice. If you don't help and/or follow Google you don't get to play, right now, because they own a large majority of most technologies being in use by the public today. That's the same thing people criticized Microsoft for.
  - zobzu 13y ago
    The point you're missing is that people don't use it because they think its good. They use it because they don't have a choice. If you don't help and/or follow Google you don't get to play, right now, because they own a large majority of most technologies being in use by the public today. That's the same thing people criticized Microsoft for. Hangout is just much more wrong tho, as you pointed out.
- Funnnny 13y ago
  SPDY isn't a trademarked technology, the name is trademarked (it should be), the protocol is not. The way SPDY works is just like OAuth/OAuth2, HTTP, XMPP work: someone invent/improve a protocol, working on draft and get it open standard. I don't see any problem with that.

threeseed 13y ago

No. You don't understand what proprietary means. SPDY is a trademarked technology owned by a private corporation. The only reason companies are adopting SPDY is because it is an improvement than HTTP. SPDY is far from perfect. The issue is that with core internet protocols this is not the way it should happen.

AnthonyMouse 13y ago
>The only reason companies are adopting SPDY is because it is an improvement than HTTP. I don't see the problem. >The issue is that with core internet protocols this is not the way it should happen. This is exactly how it does happen. Someone creates something, people like it, the creators don't enforce patents on it or try to keep it a secret, someone writes it up into an RFC. That's how internet standards are created. That's how they've been created as long as there has been an internet. Look at a counterexample. Microsoft with OOXML. Here we have a so-called standard which says things like "do this the way X version of Microsoft Word does it" without actually specifying how to do it. It's not an open standard, it's a document claiming to be an open standard on paper so that Microsoft can claim their proprietary file format is an open standard. No one else is expected to use it for any purpose other than attempting interoperability with Microsoft Office and Microsoft has no particular interest in having anyone even succeed in doing that. SPDY is not that. Google has published a reference implementation with source code. People other than Google use it for reasons having nothing to do with interoperability and Google services continue to be available to browsers without SPDY. "They didn't ask permission first" is just disingenuous griping -- who are they even supposed to have asked? SPDY isn't a problem. Hangouts are. I don't see source code for a reference implementation. I don't see anyone but Google implementing the protocol. That's how you know something is wrong.
- zobzu 13y ago
  The point you're missing is that people don't use it because they think its good. They use it because they don't have a choice. If you don't help and/or follow Google you don't get to play, right now, because they own a large majority of most technologies being in use by the public today. That's the same thing people criticized Microsoft for.
- zobzu 13y ago
  The point you're missing is that people don't use it because they think its good. They use it because they don't have a choice. If you don't help and/or follow Google you don't get to play, right now, because they own a large majority of most technologies being in use by the public today. That's the same thing people criticized Microsoft for. Hangout is just much more wrong tho, as you pointed out.
Funnnny 13y ago
SPDY isn't a trademarked technology, the name is trademarked (it should be), the protocol is not. The way SPDY works is just like OAuth/OAuth2, HTTP, XMPP work: someone invent/improve a protocol, working on draft and get it open standard. I don't see any problem with that.