478 karma · joined March 9, 2007
I can connect to Chatterous rooms using the ways I already communicate - IM, SMS, Email, etc. I don't use IRC often (and neither do most people, I suspect). For the die-hard IRC user, Chatterous is probably not that different. For people that want an easier way to chat in real-time without changing existing user behavior, it's great.
Also, an interesting story: While practicing our pitches we setup a Chatterous group for our fellow YC founders to provide real-time feedback for our presentations. It actually got to a point where people weren't paying attention to the presentations anymore and became immersed in Chatterous! We feel that Chatterous is super easy to use because of the fact that you don't need to navigate to our website, even as a Chatterous user - it's one of your IM buddies on gtalk, or an e-mail address, or an SMS short code. Think of it as IRC meets Twitter for the Hacker News community :)
However, this includes white space and comments. So probably 1/2 or 2/3 of that.
I've also heard they have Whrrl pamphlets in-store.
I wonder how they were able to partner with such a mainstream company.
On top of the SMS gateway you'd also need to rent a number or lease a short code in order to receive messages. Short codes can take up to 90 days to become active and cost ~$1000 USD/month.
There are companies that allow you to use a shared dedicated short code and have an API to deliver mobile content - some will even do this for free (http://www.textmarks.com).
His first point with respect to the up-front design needed for service interfaces - how is this any different when creating any public API that other services will consume? This is a challenge for any public interface. If the interface needs to change, mark the relevant sections as deprecated.
The second point with respect to strange dependencies - this could certainly be a problem with disparate services spread across many organizations. Again, I'm not certain that this issue is specific to SOA - it sounds like the author is pointing out that finding relevant documentation about service dependencies is the flaw here. Again, I'd like to point out that this is a challenge for any project calling on other code - documentation could be distributed across many different open source libraries, etc.
SOA definitely has its benefits. Companies such as Amazon.com have scaled successfully because of their Service Oriented Architecture, before it became a buzzword.
The author is correct, though, in stating that a lot of the buzz around SOA is bullshit. This is typical of any method/solution that receives a lot of hype. For example: http://steve-yegge.blogspot.com/2006/09/good-agile-bad-agile...