Thanks for the link. I couldn't really access the loudthinking link.
On this one, I am with David. Joel pretty much negates his point about using something battle tested and mainstream in the end when he mentions using some proprietary language for his product, which translates to a couple of mainstream languages. I don't really see the point of cross-compiling to multiple languages. The work and time invested in maintaining the proprietary language can be better invested on other critical activities. If language interoperability is an issue, thrift or message queues is there to the rescue.
Why he would use some fancy stuff when he himself is advocating using mainstream stuff is beyond me. I sure would be betting on ruby being more robust than whatever he is using in-house (preposterous claim; I have no ideas what they have in-house)
IMO the only valid complain about Ruby was lack of good unicode support at the time post was written.
On this one, I am with David. Joel pretty much negates his point about using something battle tested and mainstream in the end when he mentions using some proprietary language for his product, which translates to a couple of mainstream languages. I don't really see the point of cross-compiling to multiple languages. The work and time invested in maintaining the proprietary language can be better invested on other critical activities. If language interoperability is an issue, thrift or message queues is there to the rescue.
Why he would use some fancy stuff when he himself is advocating using mainstream stuff is beyond me. I sure would be betting on ruby being more robust than whatever he is using in-house (preposterous claim; I have no ideas what they have in-house)
IMO the only valid complain about Ruby was lack of good unicode support at the time post was written.