Re: The Delphi Brand

"Brian Moelk" wrote in message news:<45e5990b$1@xxxxxxxxxxxxxxxxxxxxxx>...

Disagree. In the context of a multiple language product like BDS, it
makes a lot of sense to rename the *language* to "Delphi" to protect the
brand from getting lost with C#, C++, etc.


Yep, I'm with Brian and Steve on this one. I'm no expert either, but I do
know that confusion is a big thing you want to avoid in branding. Codegear
has nothing but confusion in their marketing right now, including the "Delpi
for xx" issue.

Also, I'm pretty sure someone should at least be able to give a coherent
explanation of what the brand is. Given the addition of "Delphi for PHP",
is there anyone who can give a coherent explanation of exactly what "Delphi"
is? As far as I can tell, it is now just a name used to attract attention
to two different IDE's.

Delphi used to be a certain IDE combined with a certain VCL combined with a
certain language. Now it apparently includes a product with a different IDE
and a different VCL and a different language. If it makes sense to expand
the product like that, then why not rename the C# and C++ products to
"Delphi for C#" and "Delphi for C++". In fact, that would seem to make more
sense, since those products do actually share the same IDE and include
identical or compatible VCL's.

The Object Pascal/Delphi naming issue is a relatively minor one in the mix.
The problem is not just that the Delphi for PHP product uses a different
language. It's that the product has no relation at all to what has been
known at Delphi. I've said it before, it's a different IDE, different VCL,
and a different language.

It's important not to dilute the brand. It's important to make sure that
the brand stands for something identifiable. It's important to avoid
confusion. Unless Codegear can explain in a coherent way just what the
"Delphi" brand is supposed to identify, then they'll likely end up diluting
the brand and damaging themselves. And please don't just tell me that it's
supposed to identify a friendly IDE with an easily usable library of
components. Up until now it's always stood for a particular IDE with a
particular VCL, combined with a particular language. Codegear can try to
change that, but it's dangerous. And it makes little sense if "Delphi" is
now just going to mean any friendly IDE with a component library.

Much better would be to concentrate on building up the "Codegear" brand.
Imagine that. That's what you do if you're planning to be around for the
long haul.

-- Herb





.

Relevant Pages

  • Re: The Delphi Brand
    ... CG Delphi is a brand and a language. ... Meanwhile, I have recieved an email about Delphi for PHP,and ... PHP is just another programming language. ... "Borland Delphi" is a brand. ...
    (borland.public.delphi.non-technical)
  • Re: Moving to C#
    ... > are still some concepts that neither language do particularly well. ... language parts inside Delphi). ... > What matters more to me is the quality and functionality of the IDE. ... C#Builder then I doubt it will actually play any role for C# developers. ...
    (borland.public.delphi.non-technical)
  • Re: A lesson for Real
    ... and I really only know Basic and Ruby. ... perfect language for me, ... Delphi, RB, and VB. ... I actually like the IDE of RB2005. ...
    (comp.lang.basic.realbasic)
  • Re: Chrome - competition for Borland?
    ... Ultimately the goal would be to have everything in a single language, ... in a single IDE, and Chrome would be a stepping stone to that goal ... Delphi would be for legacy, but for that task, there is already D7. ... basic Windowing support and native compilation in some areas (latest batch ...
    (borland.public.delphi.non-technical)
  • Re: The Delphi Brand
    ... name of its version of Object Pascal to "Delphi" to match the name of the ... IDE product in which it was housed. ... the company was forming plans to introduce multiple language personalities ... called Borland Developer Studio or Turbo. ...
    (borland.public.delphi.non-technical)