This paragraph is part of the Java Performance tunning newsletter
someone sent to me. I'm curious what the article means
in regards to threads. My Ruby book has a section
on threads, but I'm not sure if threads in Java are vastly different ?

"So many people have been shouting at me that "Java has peaked,
time to jump into Ruby" that it was time to find out about the
hype. So I listened carefully to Ruby advocate Tim Bray. I found
out that Ruby will reduce maintenenance costs because it takes a
third of the lines to express the same things as in Java. That's a
big plus. But I also found out that Ruby is not going to be able
to handle any significant part of the hugely concurrent multi-
threaded apps that I tend to deal with - apps that are the present
and future of programming. Sounds pretty restrictive. I listened
when Elliotte Harold tells me that Java developers are looking to
Ruby and Rails - but then I spoke to some Java developers who have
made that move, who tell me that it's a great system to get that
initial prototype up and running, but that they end up with a mess
when they try to advance the system. "