From: Francis Cianfrocca Date: 2006-10-07T13:10:44+09:00 Subject: Re: Enterprise-Ruby Wish List by Francis Cianfrocca ------=_Part_32872_16070543.1160194240955 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline On 10/6/06, David Vallner wrote: > > (snip) > Also, the overgeneralising vaguely to nag at [insert name of language > that isn't Ruby here] doesn't quite make me trust you more as a > technology journalist. It comes across as so much cheap > community-pandering. > > If you have nothing good to say... > > David Vallner > (Can we -finally- stop with the cheap shots at not-Ruby?) I stand by my point, expressed in the InfoQ piece, that there are several areas of enterprise infrastructure that are lacking in demonstrable ways. One of them is message-queueing, a core technology for application integration that is, in my opinion, seriously underused due to lack of real understanding of its capabilities, and also challenges with the available tools. Most of the enabling technology used in message-oriented integration today is proprietary and not open, frighteningly expensive, and not interoperable (by design). ActiveMQ is a very valuable, impressive, and competent step in the direction of opening things up. I won't try to convince you or anyone else that ActiveMQ is not suitable for all uses, and that there is room for an alternative or two. Why should Rubyists consider creating such an alternative? Because of Ruby's unique attributes, and also because of the stylistic conventions that have evolved in our community, a Ruby-based alternative may be better in measurable and meaningful ways, particularly regarding ease of deployment, configurability, and integration with other technologies. One size doesn't necessarily fit all. What are my qualifications to say things about message-queueing that you don't want to hear? I've designed several commercial MQ systems over the last ten years that have met with commercial success. I've designed both wire protocols and APIs for MQ, going back long before JMS or Jabber were invented. I come to this forum to learn new things that I didn't know before. You haven't said anything that qualifies so far, but I'm still listening. ------=_Part_32872_16070543.1160194240955--