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.
Thank you for reading this Techdirt post. With so many things competing for everyone’s attention these days, we really appreciate you giving us your time. We work hard every day to put quality content out there for our community.
Techdirt is one of the few remaining truly independent media outlets. We do not have a giant corporation behind us, and we rely heavily on our community to support us, in an age when advertisers are increasingly uninterested in sponsoring small, independent sites — especially a site like ours that is unwilling to pull punches in its reporting and analysis.
While other websites have resorted to paywalls, registration requirements, and increasingly annoying/intrusive advertising, we have always kept Techdirt open and available to anyone. But in order to continue doing so, we need your support. We offer a variety of ways for our readers to support us, from direct donations to special subscriptions and cool merchandise — and every little bit helps. Thank you.
–The Techdirt Team
Filed Under: appengine, copies, web 2.0, web platform
Companies: google
Reader Comments
Subscribe: RSS
View by: Time | Thread
AJAX/Comet?
Python-friendly?
Any chance of getting that article rewritten for those of us not steeped in web 2.0 lore?
Cripes, I now know how my grandma feels when she says, "I don't see the anykey. Where's the anykey?"
Time to go yell at some young whippersnappers on my lawn. They must be texting each other or something.
[ link to this | view in thread ]
AJAX Comet is a massive comet many believe will destroy the earth. you're advised to build a bomb shelter.
python-friendly is the name for the great internet snake which is threatening net neutrality
[ link to this | view in thread ]
LOLROTFPMPCADABHKHJSAHDL
Seriously some funny stuff! Well thought out, great delivery. I give you a 9.8
[ link to this | view in thread ]
SaaS = software as a service
AJAX = asynchronous Javascript and XML; check the link for Comet. Both are techniques for updating browser contents without reloading the page, and both are heavily used by Web 2.0 apps to provide seamless, native application-like experiences.
Python is an interpreted programming language that is used for scripting and web development; it competes with Ruby and Perl, among other languages. Google is heavily invested in Python, and consequently App Engine is oriented toward its use. Ruby, which is used by 37Signals and many others, has been the hot web language for a while now (despite having serious performance issues). I expect Python programmers to suddenly find themselves in high demand as a result of App Engine.
[ link to this | view in thread ]
Must not contradict 37signals
[ link to this | view in thread ]
Shagger Green lasers rulz
[ link to this | view in thread ]
Re:
texting?
They're probably snapping whips, ya old fuddy-duddy... go take away the whips!
[ link to this | view in thread ]
Laser Pointer
[ link to this | view in thread ]