Incremental Web vs Radical Wave
Upgrades to the web are incremental. Instead of requiring a complete overhaul of your technical infrastructure, or radical changes to existing behaviors, the web tech that wins is usually the sort of thing that can be adopted piecemeal, integrated as needed or as a normal part of updating one's websites or applications. Understanding new tech needs to be a weekend-sized problem. For a lot of web developers, long before they start integrating a new protocol or platform into their work, they hack together a rough demo over a long weekend to make sure they truly grasp how it works. And a weekend-scale implementation on a personal site usually translates roughly into a 90-day implementation cycle in a business context, which is a reasonably approachable project size. (In tech, three days in personal effort often translates to three months of corporate effort.) There has to be value before everybody has upgraded. This is basically a corollary to Metcalfe's Law. While we know networks increase in value as they add more nodes, the nature of web tech is that, in order to be worthwhile, it has to provide value even if the people on the other end haven't upgraded their software or web browsers or clients or servers. Otherwise you're shouting into an empty room. You have to be able to understand and explain it.
via dashes.com
What's new about Wave?
* Powerful realtime collaboration features
* Unlimited versioning of content
* Built around robust XMPP protocol
* Combines chat, document editing, and message threading — wikis + blogs + comments + IM
* Delivered as a very polished rich user interface
What makes Wave great?
* Federation (XMPP)
* The robot protocol (JSONRPC)
* The gadget API (OpenSocial)
* The wave embed API (Javascript)
* The client-server protocol (As defined by GWT)
via dashes.com
