I think even messaging has become less and less of a detriment.
Reliable Messaging from Assaf Arkin gives you a solid pure-Ruby option
and stomp gives you the ability to talk to ActiveMQ servers (and
there's a new library that's being worked on for the new fangled
messaging dealies from Java).

All in all, I think messaging is less of a detriment.

Though, soap4r has made me kill small animals before out of
frustration.  That should probably be fixed, eh?  Google SoC anyone
(even though it's too late)? ;)

--Jeremy

On 3/29/07, Alexey Verkhovsky <alexey.verkhovsky / gmail.com> wrote:
> OK, I'd like to ask about technology problems. Specific obstacles that make
> Ruby either less appealing, or not at all feasible on some corporate IT
> projects.
>
> So far, only messaging was mentioned on this thread.
>
> The other thing people on ThoughtWorks Ruby projects complained about was
> continuous integration. CruiseControl.rb is our solution to that problem.
>
> We also hear some bitching about production deployment. I think with the
> advent of Mongrel it's much less of an issue, but it's been a fast moving
> target over the last couple of years, and new people find it hard to figure
> out the current state of the art.
>
> What else?
>
> --
> Alex Verkhovsky
>


-- 
http://www.jeremymcanally.com/

My free Ruby e-book:
http://www.humblelittlerubybook.com/book/

My blogs:
http://www.mrneighborly.com/
http://www.rubyinpractice.com/