This post originated from an RSS feed registered with Java Buzz
by Bill de hÓra.
Original Post: A reasoned response to Scala/Ruby at Twitter...
Feed Title: Bill de hÓra
Feed URL: http://www.dehora.net/journal/atom.xml
Feed Description: FD85 1117 1888 1681 7689 B5DF E696 885C 20D8 21F8
Alex Payne: "Make things, measure them, have reasonable and respectful conversations
about them, improve them, and teach others how to do the same." - Mending The Bitter Absence of Reasoned Technical Discussion.
as far as the current Ruby/Scala "debate" goes - I would say always bet on protocols and formats, the web being the prime example. Because as someone who likes Twitter immensely, I like that I don't have to care too much what Twitter is written in or what it runs on. I like that behind the server, the entire stack can be swapped out or ground up rewritten as the service owner sees fit, and as seems to happen with many popular Web services as they grow. That the Twitter API can persist across such internal upgrades is a wonderful thing. This is possible because on the Web, programming languages are an implementation detail. Including javascript/actionscript code on demand.