Thanks Razano for sharing this. I have the following comments/ideas after watching this demo 3 times:

1. I expect it would be difficult without the current email, IM, chatting and discussion platforms we already have to come up with the wave concept that combines all of these different functionalities. 

2. The demo shows very well how modeling can help: The main developer just showed us at the very beginning a model of the email, and how the "message" as an object flows from this to that, while in Google's wave model, people visit the wave rather that it travels to them. S, my point is: It is a very powerful technique to model things after being created, identify their different dimensions, and starting to play with those dimensions, or creating some new.

3. The demo showed how it is important (at least in the Software realm) to be concrete. If we can model the the email class as something that has a sender, a recipient, and content, then Google's developers didn't just say: let's change that. NO, they "said": let's create something that has an originator, multiple recipients, it is editable in many parts, can be viewed in many forms, etc. I am saying this, as some those who want to start new things, projects, etc tend to stop at the abstract level, without taking their ideas, projects into the concrete level

4. The demo showed us the interplay of ideas/tools. Some of whom I know tend to emphasize the role of ideas, and think of the tools as "exterior", not essential to further develop the idea. The developers, in their demo, showed us two things:

1. How it was "almost impossible" without GWT (a framework of software tools developed by Google) to take the wave concept and make it real.
2. How some "old perceptions, influenced by old tools" have an effect that can hinder thinking of the new concept, even for the people who came us with the new concept.