Daniel Pitts wrote:
Although, I don't typically think of this as a problem I need to solve
often. How is ruby at real problems, like writing a web app that can
handle 60+ million hits per day?
How about a system to take in >100 million documents in a matter of weeks,
parse them for adherence to certain surface edits, then pass them on to a
mainframe for further processing, load-balanced across geographically
disparate server farms, each server with 32 CPUs, programmed by several teams
with a few dozen developers overall, and have no downtime?
I'm working on one of those now, and it's in Java (JEE). Could Ruby deal with
that, I wonder?
Static type-checking alone probably saves my customer a few hundred million
dollars a year.
Jet liners are the cat's meow when you have too many passengers to fit on a
hang glider.
--
Lew
Indeed. For prototyping, I'd probably choose Python over Ruby
Or, I would use the built-in Rhino engine. JavaScript is actually a