5 ms·
Google Wave does not solve problems directly, just like SMTP/POP/IMAP per se does not solve the problem of communication. You need email client to communicate o
by smikhanov 17y ago
Google Wave does not solve problems directly, just like SMTP/POP/IMAP per se does not solve the problem of communication. You need email client to communicate over SMTP/POP/IMAP, and the better your client is the better you deal with your problems (e.g. Outlook's feature of transmitting the messages of predefined format over SMTP to all the appointment participants helps you manage appointments).
When Wave will be public, I expect plenty of different Wave bots, clients and other type of software appearing out there. This Wave-based software will solve real problems, not Wave itself.
- swombat 17y agoGranted - but I would say the default Wave client already solves a whole host of problems. Remember, Wave is composed of the protocol, the server, and the client as well. If the Google Wave client as it is now is used as a starting point for future Wave clients, then they will all benefit from these features. Conversely, clients that don't solve the problems that Google's reference client solves are effectively inferior.
- jaaron 17y agoI think you're mixing up wave. Wave _is_ an actual application, not a protocol. It uses several protocols to get its job done, but it _is_ an application. And the wave code is already public: http://code.google.com/apis/wave/ http://code.google.com/apis/wave/
- smikhanov 17y agoSure it's an application, not a protocol. However, I still think that it's not the current application that will deliver most of the Wave's value. Just like it's not the Twitter website that delivers most of the value of Twitter, but the ecosystem of the clients using its API.
- richardw 17y agoThink light wave - sometimes it's an application and sometimes it's a protocol. da-dish
- elblanco 17y agoProtocol Specs http://www.waveprotocol.org/ http://www.waveprotocol.org/