Slogan/catchphrase for D?

Nick Nick_member at pathlink.com
Fri Mar 24 02:23:23 PST 2006


In article <dvr3n6$2u4$1 at digitaldaemon.com>, Walter Bright says...
>
>If you could  sum up the essence of D in a "high concept", what would it be?
>
>http://www.themegahitmovies.com/highconcept.htm

Well, what are the key positive points you would like to express? What makes D
special? After reading through this thread, I'd have to say the best suggestions
so far are

- "The fastest way to fast code", and

- "Speed with ease", perhaps somehow in combination with "Have it both ways".
Eg. "Fast and easy - have it both ways"

The key words here are speed/fast and easy (I don't like 'simple' since it has
other negative connotations, ie. unsophisticated.) The phrase should probably be
built around those words/ideas. It also is not a bad idea to have some reference
to the programming world, words like "code", "write", "run" to make the phrase
look less generic, but it's not mandatory. Some other suggestions:

- Don't refer to C++ or Java - never a good idea to refer to your competitor, it
looks like the only argument you've got is "At least we're better than THEM."

- Don't use words like "bug" or "debug", they are _negative_ words. Instead use
positive words, like "safe" or "secure".

- Avoid jokes and play on words like "D-code" or "D-licious", unless you can
make it look really good.

- Keep it short and snappy, no two-sentance catch phrases.

Catch phrases (and other marketing gimmicks) are sort of like the feathers on a
peacock. They don't really serve a purpose, they are mostly signals companies
use to say "Yes, I'm big and powerful enough to hire a competent marketing firm.
Pick me." IMO the most important quality of a good catch phrase is that it
doesn't look goofy. If it looks like something a 14-year old made up, people
will think the same of the whole D language.

This doesn't mean one can use all kinds of silly/funny phrases to market D, but
the one "official" catch phrase should look professional.

>Some particularly bad ones:
>
>1) Write once, debug everywhere
>2) Tastes great, less filling.
>3) Choosy programmers choose D.
>4) C's dead, Jim.
>5) So sophisticated, even we don't understand it.
>6) Resistance is useless.

Yes, these are really bad :-)

>1) Power, Performance, Productivity

Can you say boooring?

Nick





More information about the Digitalmars-d mailing list