From: Todd Benson <caduceass@...>
Date: 2008-08-24T05:17:32+09:00
Subject: Re: A Mascot...

On Sat, Aug 23, 2008 at 7:16 AM, MRH <mauriceroman@gmail.com> wrote:
>>On Aug 20, 3:13 am, Mayuresh Kathe <kathe.mayur...@gmail.com> wrote:
> (SNIP)
>
> If Ruby needed a mascot it would have one by now. This attempting to
> force it to have one is a silly waste of time.
>
> (back to the code - which is what matters)

You obviously haven't studied marketing/branding.  To hope that the
ability of a program/OS/library stands on its own is only partly true.
 Exposure is best for everyone in the long run, and the picture of a
"ruby" cut gem doesn't cut it.  It shines but is ultimately inanimate.

If you only want to attract intellectuals, then by all means, omit any
kind of mascot/branding.  I'm fine with that.

I can foresee a problem with a cute female mascot, simply from other
programming camps (hey, look!
"picture_of_ruby-chan_cheerleader_upskirt.png") proliferated on python
lists to point out naivety and an exposure type nature.  Now, you
could apply this ploy with pretty much anything, but the whole cutesy
girl thing makes that chance easy (pun intended?)

I don't want to go into other things of what a python could do with
ruby-chan exemplified in manga comics to make the Ruby language seem
inferior.

I did like the idea of the raccoon though.  But, then you could
scandalously destroy that one, too, with a simple cartoon of a raccoon
reaching for a shiny ruby in a hand trap.  Apparently, the real life
raccoon has a hard time letting go of something.  Fist gets big, won't
let go, and barbs in the trap pointing into the trap hole depths
capture the critter, because among it's kind, stubbornness abounds.
Analogy: programming freedom sought, but lost in the end via a simple
trap.  You can see that argument coming from a mile away.

I don't like the sound of that now that I think about it.

Meerkats, anyone?  j/k

Todd