This is Zie/Lassina (For those who have not met me yet, I’m with Flat
Toads Inc. was recently with Ross)
Charlie, long time no talk...
This was indeed a good read.
As a developer that has been part of the sandbox since July, I think
wave will steadily succeed. The article makes some great points
however, Google has already taken care of those alleged setback noted
or they are simply not factors that will impact the success of wave.
(of course this is just my point of view)
The only one thing I can see wrong with wave is the FriendFeeds-like
roll out. Although it is a good strategy on paper, it has proven not
to be so great in reality. In Friendfeeds' case developers were not
presented with true incentive unlike for example; the iPhone. I don’t
see millions of developers jumping on the wagon either or company
adopting the service because they hope to make a “large junk of cake”,
that has proven to be an important factor on the iPhone technology.
However, because we are talking about the Big G this will be a success
even without advertisement.
The article argues-
Federation (XMPP)
The robot protocol (JSONRPC)
The gadget API (OpenSocial)
The wave embed API (Javascript)
The client-server protocol (As defined by GWT)
Xmpp/jsonrpc,
The article argues that XMPP alone is a bear to implement, let alone
to deploy at large scale. I can relate, however Google has released an
api that takes all the work away from the developer. Robots can now be
builds on a on top of Google’s ready-to-use tools. I have implemented
this for a high school and deployed it in about an hour. (it could
have taken me 25 min, if not for my failure to notice some simple
syntax.) This is just to say that the documentation is good and so it
was helpful. This is most of the article’s arguments. Scaling is no
concern either because the application is hosted on Google’s
infrastructure.
Pushbutton VS xmpp
The pushbutton technology reference was also rich. As we all know web
2.0 today, websites aren’t simply web pages anymore they are
applications. Browsers like chrome and Firefox are become standards on
every machine while HTML5 takes over. For the next 5 years, I’m
expecting rich stuff, browsers like chrome (itself being open source)
will be able to load pages like I was turning the page of a book. With
that being said as a developer, I’m looking for the best technology I
can get my hands on since it is only getting more innovative. If I can
use xmpp (a clearly better technology) as a protocol, heck I will.
This new protocol
Federation
Google has put massive amount of resources in federation RnD’s
(research and development); We have all seen and benefit from their
federated authentication standards. With so much documentation and
api’s available for devs to use, federated logins is nothing for the
overage web designer these days. You want your app to play with wave?
You don’t have to do anything but use the search engine. I’m part of a
10-year+ google/ibm cloud initiative RandD and grant, one must give
props to those guys.
As you guys remember Anil Dash’s article when you discuss “What Makes
a Successful Project?” here is a link to this same article by George
Pór. ttp://
tinyurl.com/wavewillsucceed. You can take away points from
both and sum up your own conclusion. Again, those are just their
personal opinions and so is mine.
Thinking out loud though…
Will this new protocol play with Filemaker? A reason and a purpose.