------art_20368_14297387.1159982992131
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

On 10/4/06, Joel VanderWerf <vjoel / path.berkeley.edu> wrote:
>
>  Why no mention of http://www.pragmaticprogrammer.com/titles/fr_eir/ ?



I'm guessing that you're asking why I didn't mention that book (or any
other) in my piece. The short answer is that the piece is a survey of
existing infrastructure, not a literature survey. A slightly longer answer
is that I was trying to address needs that are faced by enterprise
developers *in general,* not needs faced specifically by Ruby developers. I
think that enterprise software infrastructure can benefit from some new
components written in Ruby, *irrespective* of whether the development
language you subsequently choose for any given project is Java, Ruby, or
something else. As always, "use the best tool for the job," and I'm trying
to explore whether some new enterprise-class infrastructure can, and should,
be written in Ruby rather than the default choice (Java).

A small example: let's say you're a Java programmer accustomed to using JMS.
If I offered you a message-queueing product that supported JMS but was
"better" in measurable and compelling ways than what you use now (and
parenthetically happened to have been written in Ruby), wouldn't you want to
give it a try?

------art_20368_14297387.1159982992131--