Anil Dash wrote that the Wave as a too complicated protocol to implement. Anil writes that nobody but Google will create a waveplatform because it is too complex to implement.
“But the fundamental Wave protocols are, I fear, a bit too complex to ever be fully and correctly implemented by anyone other than Google. Interoperability is likely to be a challenge that plagues the platform for its entire existence. In short: It’s likely that nobody will ever build a fully-compatible clone of Wave that competes with Google’s own implementation.”
Yes it is more difficult to write a federate wave application, that to use the Twitter API for communication. But don’t we (as humans) have the ability to implement complex protocols.
How about SMTP created in 1982 with an RFC, a document on 67 pages. I don’t think that I’m able to get an SMTP server up and running on a weekend, as is Anil’s time for a easy implementation. You also needed to considere how TCP/IP worked before you could implement the SMTP protocol. The wave protocol draft specification is 24 pages (when I copy the text to Word), so it is not longer. If the complexity together with XMPP is larger I cannot say.
When talking about open specifications and complexity. Then the winner must be OOXML or ODF, I don’t know the size of this specification but people are fighting to create some useful specifications that others will implement. I don’t know how many will implement the standards Microsoft and OpenOffice, but it is open if people want to implement features into them.
Agreed we will not see a lot of providers of Wave servers developed by third parties. But some have already started with developing clients as open source projects and there will probably be more projects. We will probably also see some software providers, how will implement and sell their own version of wave servers/clients, so you can have the privacy of on premise solutions.
Another area where there are specifications and multiply providers is in the J2EE world. Sun created a speciation of how ie. J2EE 5 should work and then multiply developers created their version of an application server. In this area we have Sun, JBoss, SAP, (Oracle) and countless other servers.
Sure I would like the Wave protocol to be as easy to program as Twitter, but then we have not created a solution which could revolutionize communication.