From: Gregory Brown <gregory.t.brown@...>
Date: 2006-02-21T03:21:41+09:00
Subject: Re: Don't let this happen to Ruby, pleeeeease?

On 2/20/06, Dave Howell <groups@grandfenwick.net> wrote:

> I'm sure if I spent more time not trying to actually get work done, I
> could get that fixed, by asking questions here. But I have a copy of
> Pickaxe, so I just use that. If I have to spend time working on my car
> instead of driving to work, then my car isn't very good. If I have to
> spend time working on my computer instead of using it to get work done,
> then my computer's not very good. And if I have to spend time sending
> messages to Ruby-Talk trying to find out how to get Ruby to work
> instead of programming, then Ruby's not very good.

Ruby is not about being very good.  It's about world domination.

    (C)M AT Z(S): How are you gentlemen !!
    (C)M AT Z(S): All your base are belong to us.
    (C)M AT Z(S): You are on the way to destruction.
    Captain: What you say !!
    (C)M AT Z(S): You have no chance to survive make your time.
    (C)M AT Z(S): Ha Ha Ha Ha ....

See...  thats matz... er... Cats... laughing at you.  Move Zig!

On a serious note though, for an emerging language that only fairly
recently became popular in english speaking countries, I think Ruby is
great in terms of support.

If talking to people on #ruby-lang or RubyTalk or searching archives
and using a little google fu is not something you can afford right
now, no big deal.  We'll still be here if you decide to come back
later on.

As a library developer (working on relatively small things at that),
I'd love to have some awesome documentation.  Time constraints slow
that process.  I can only imagine what those constraints are like on
the big things.  So... just be patient.  Or whenever you do end up
having to search a little deeper for something, write down what you
did and build a little tutorial.  The community will appreciate it and
it'll help overall.