Much Ado About Nothing: The Rise And Fall Of HuddleChat
from the harping-on-huddlechat dept
If you've heard of HuddleChat at all, you already know about its demise. Put together by a few Google engineers in their spare time, the web chat application was used to showcase Google's newly-announced App Engine offering. There was just one problem: it was nearly identical to 37Signals' Campfire, a well-known SaaS web chat application. 37Signals gave some petulant quotes to ReadWriteWeb about the situation, and shortly thereafter Google pulled the app down.
As Om Malik has pointed out, this is all a bit ridiculous. AJAX/Comet chat is a fairly simple feature to implement. If my fellow participants in the Web 2.0 economy are counting on earning their keep via a collective conspiracy to make our jobs look harder than they are, we're all in deep, deep trouble. There's additional potential irony here, too, given that 37Signals has been accused of ripping off others' work to create Campfire in the first place.
But while this incident may prove portentous to the long-term prospects of the 37Signals business plan, it's hard to see how it could mean anything for Google. Breathless declarations that "many in the developer community [will] view Google App Engine as a Xerox machine for copycat product developers" are downright laughable. Google's decision to kill HuddleChat makes good PR sense, but it's inconceivable that many cost-conscious, Python-friendly startups would give up on App Engine over this minor blog imbroglio. As in many other respects, Amazon Web Services will likely provide the relevant template for these issues, and so far AWS has wisely avoided getting dragged into policing its users' apps.
Of course there's a lot of speculation that App Engine will include a free offering, and for that reason it may attract more troublesome users than EC2 currently does. But even if Google finds itself obligated to fight more griefers, phishers and spammers than Amazon does, it seems certain that they won't waste their time arbitrating squabbles over who called dibs on which trivial featureset. Sadly, that will remain for the courts to decide.