It seems to me that the entire key to having this whole thing work out is if we have as many of these as possible. I think it's great that these guys were willing to put in the effort before Google even brought their product to market. We're looking at a parallel dual network effect here: the product/client (ie, barring any unforeseen, giant occurrences, Google's client) will only take off if it manages to establish a large userbase for an unproven product. BUT: Wave, as a protocol, as a server type—as a web technology rather than a Google tool—will only take off if it manages to establish a large codebase of clients and servers for an unproven protocol. As far as I can tell the one thing that will have the biggest effect in a) ensuring Wave's success and b) actually IMPROVING Wave and shaping it according to the needs of the web at large is if as many people as possible do what PyGo has just done first.
Comments
It seems to me that the entire key to having this whole thing work out is if we have as many of these as possible. I think it's great that these guys were willing to put in the effort before Google even brought their product to market. We're looking at a parallel dual network effect here: the product/client (ie, barring any unforeseen, giant occurrences, Google's client) will only take off if it manages to establish a large userbase for an unproven product. BUT: Wave, as a protocol, as a server type—as a web technology rather than a Google tool—will only take off if it manages to establish a large codebase of clients and servers for an unproven protocol. As far as I can tell the one thing that will have the biggest effect in a) ensuring Wave's success and b) actually IMPROVING Wave and shaping it according to the needs of the web at large is if as many people as possible do what PyGo has just done first.