[ocaml-biz] logos vs. mascots

[Brandon J. Van Every]

Brian Hurt wrote:
>
> The problem with thinking in terms of "mascot" is that
> implies a plushy
> toy market.  Linux is the first software project with a
> plushy toy mascot
> that has gained any industry acceptance that I can think of.  And, if
> anything, having a plushy toy mascot has probably hurt it.
>
> Windows has a logo.  Java has a logo.  I'd much rather Ocaml
> have a logo than a plushy toy mascot.

I would definitely say, design a proper business logo *first*, have a
plushy toy mascot contest *later*.  The two should not be confused for
each other.  Plushy toy mascots are good techie marketing, along with 3D
demos of camels dancing on cams, and other sorts of 'schwag'.  But
techies aren't the only demographic that needs to be marketed to.  A
logo needs to be taken seriously by all comers.  Techie, suit, and
academic.

The logo is far more important than the mascot.  The mascot is a mere
implementation detail, the byproduct of some yet-to-be-run contest.

Incidentally, when the time does come for such a contest, it should have
one ground rule.  "All mascots bearing a suspicious resemblance to Joe
Camel will be immediately and unflinchingly disqualified."  And if
anyone bitches and moans about that, cite the legal reasons.


Cheers,                         www.indiegamedesign.com
Brandon Van Every               Seattle, WA

20% of the world is real.
80% is gobbledygook we make up inside our own heads.