3 ms·

It's a shame, really. Even in my job nobody seemed to "get it" when i tried to explain benefits and the "real" nature of wave (that it's a protocol). And i'm wo

by buster 16y ago

It's a shame, really. Even in my job nobody seemed to "get it" when i tried to explain benefits and the "real" nature of wave (that it's a protocol). And i'm working in a heavily messaging (mail, etc.) oriented company. I got everyone beta accounts and yet nobody got it. It was all about the sandbox/webclient. I think Google did a lot wrong with the promotion of wave. Anyway, i'm eagerly waiting for the completion of the incubator process on apache[1] and will take another look at the state of wave afterwards. I still think the project is one of the most underrated projects of the last years. I very much hope that the project won't just die. [1] http://www.waveprotocol.org/wave-in-a-box/apache-incubator-roadmap http://www.waveprotocol.org/wave-in-a-box/apache-incubator-r...

jasonlotito 16y ago
I am right there with you. I now exactly what you are talking about. Every time I hear someone dismiss it, they dismiss out of ignorance. I've never heard otherwise, even from some otherwise smart people.
axod 16y ago
Anyone can write a protocol though. That's the easy bit. They failed to create a killer product.
- buster 16y ago
  First of all, i'd say designing a _good_ protocol is pretty much the hardest and smartest work to do. Of course everyone can design a protocol to send a messange from A to B. But you really think it is something _that_ easy to design a complete protocol for messaging between a wide variety of clients and servers? Take as much as possible usecases and edge cases into account and make it really good? If it would that easy SMTP wouldn't have a big pile of extension RFCs. Everyone can write a website that let's people chat in groups, right? I mean.. really... THAT is easy. ;)
  - axod 16y ago
    I agree with you. Writing protocols, websites, creating new programming languages... all relatively simple. Getting people to use what you built is the hard bit.

by buster 16y ago

jasonlotito 16y ago

I am right there with you. I now exactly what you are talking about. Every time I hear someone dismiss it, they dismiss out of ignorance. I've never heard otherwise, even from some otherwise smart people.

axod 16y ago

Anyone can write a protocol though. That's the easy bit. They failed to create a killer product.

buster 16y ago
First of all, i'd say designing a _good_ protocol is pretty much the hardest and smartest work to do. Of course everyone can design a protocol to send a messange from A to B. But you really think it is something _that_ easy to design a complete protocol for messaging between a wide variety of clients and servers? Take as much as possible usecases and edge cases into account and make it really good? If it would that easy SMTP wouldn't have a big pile of extension RFCs. Everyone can write a website that let's people chat in groups, right? I mean.. really... THAT is easy. ;)
- axod 16y ago
  I agree with you. Writing protocols, websites, creating new programming languages... all relatively simple. Getting people to use what you built is the hard bit.