> And that listings of uses of Ruby in commercial projects represents
> only part of Ruby's success.
>

If you can convince a manager who doesn't know programming but likes
to think he does that something without commercial cred is better than
something PHP or Java (i.e., one of my former managers), then I will
give you a sack of money.

Or a hug.  Whichever is cheaper. ;)

It's sad that was what decisions came down to for him (and one other
persoon Ive worked with), but it's a reality.  And something that can
be easily addressed by (a slightly better version of) this little
list.

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

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