I really don't think a catchy name would have helped in your case. Your
management, like many others, prefer to "manage by magazine". And we all
know who is in all the magazines.
If your management did not like Perl, why not try java, c or php?
If your management did not like MySQL, why not Postgres, Sybase, Oracle,
Informix?
My point is it would not matter. The issue was not Perl, the real issue was
that it was not a Microsoft product.
----- Original Message -----
From: "Chris Thompson" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Tuesday, January 29, 2002 5:29 PM
Subject: Re: New mod_perl Logo
> On Tue, 29 Jan 2002, Jonathan M. Hollin wrote:
> > Ideas for logos, banners, "powered by"-type buttons are all welcome.
>
> Well, I'd like to just throw one idea into the mix. It's something that's
> bugged me for a long time, no better time than the present.
>
> "mod_perl" is a lousy name.
>
> There, I've said it.
>
> For any number of reasons, perl does now and will always face an uphill
> struggle in any "Enterprise" application.
>
> For example, at my place of employment, we just went through a rather
> arduous task that I fought against and lost.
>
> We had a production site that handled a decent amount of traffic. Apache,
> mod_perl, Linux and MySQL. It ran and ran with almost no intervention.
>
> The management team of the company that bought us a year ago had been
trying
> to force a change in the product by throwing up various arguments, which
> were always false. ("MySQL doesnt support Transaction", "Yes it does".
"But
> they arent atomic.", "Yes they are". "Well, you can't roll them back.",
"Yes
> you can.")
>
> In the end, I lost. From October to mid January they set about taking our
> fully functional product and "replatforming" it to Win2k/IIS/ASP+VB/MSSQL.
> The final reason? "Responsible enterprises do not use perl."
>
> mod_perl needs a name. Something marketable, something catchy. The java
> folks learned that a long time ago. Their systems are called
> "Tomcat/Jakarta" and "Cocoon" and "Resin".
>
> THAT, in my opinion, is what should happen for mod_perl 2.0. It should be
> "Adirondack" or "Orwell" or any other generic, innocuous name. Even
> "MonkeyButter v1.0" is probably a better deal than mod_perl.
>
> As for logos, Avoiding Camels or Eagles is a requirement. I don't blame
ORA
> for requiring the trademark notices, the twisted concepts of US trademark
> law REQUIRE them to do that. The first time they didnt, they could lose
> their trademark. But we should have a "mascot" that makes sense and is
OURS.
> Linux has the penguin, OpenBSD has the blowfish, the other BSD's have the
> devil. Those images are clearly associated with those products, and can be
> used WITHOUT corporate approval.
>
> --
> _______________
> Chris Thompson
