Re: Delphi bugs and "moving" to Visual Studio debate

> I read it as 2, and now I guess you really meant 1.

That is correct. IMO, intepreting it as 2 makes some assumptions about
motive.

> I think Borland did
> it because they thought it was a good idea.

Ok, and to go further...why do you think Borland thought it was a good idea?

> Note that that was in the
> times of Inprise, IIRC.

Was it? I'm not so sure about that. Even the origins of the name Delphi
ties it to Oracle.

http://community.borland.com/article/0,1410,20396,00.html

" The strategic decision to make database tools and connectivity a central
part of the new Pascal product had been made only a few days before, so Gary
was keen on having a codename that played up the new database focus of the
proposed product, and of its development team. The database shift was no
small matter - I remember having grave reservations about "polluting" the
Pascal tools with database arcana that took me almost a year to shake off.
It was a big gamble for Borland, but it was very carefully measured,
planned, and implemented. In hindsight, making Delphi a database product was
exactly what was needed to break Borland's Pascal tools out of the Visual
Basic - C++ market squeeze play and set Delphi head and shoulders above
traditional Windows development tools.

Gary kept coming back to the codename "Oracle", referring to SQL
connectivity to Oracle servers. "Oracle" didn't fly with the group, though.
Aside from the obvious confusion with the same-name company and server
product, the name itself implied server stuff, whereas the product we were
building was (at that time) a client building tool, a way to talk to Oracle
and other servers.

How do you talk to an oracle? "The Oracle at Delphi" was the word
association that popped into my head. So I offered up "Delphi": If you want
to talk to [the] Oracle, go to Delphi."

--
Brian Moelk
bmoelk@xxxxxxxxxxxxxxxxxxxxxxxxxxxx
http://www.brainendeavor.com


.

Relevant Pages

  • Re: Best way to updat TNSNames.ora in all servers
    ... We have many unix servers running Oracle ... database 9.2.0 enterprise edition. ...
    (comp.databases.oracle.server)
  • Re: Best way to updat TNSNames.ora in all servers
    ... We have many unix servers running Oracle ... database 9.2.0 enterprise edition. ... could justify for having many installations of Oracle 9.2.0.x would be ...
    (comp.databases.oracle.server)
  • Re: Delphi bugs and "moving" to Visual Studio debate
    ... mention to them that Delphi is named Delphi because it was to ... development environment for Oracle, ... item 3 (database) is the primary factor for decisions. ... > clients don't even know about any bugs etc in IDE's before they decide ...
    (borland.public.delphi.non-technical)
  • Re: Best way to updat TNSNames.ora in all servers
    ... We have many unix servers running Oracle ... database 9.2.0 enterprise edition. ... could justify for having many installations of Oracle 9.2.0.x would be ...
    (comp.databases.oracle.server)
  • Re: Myths of our time...
    ... especially in the database area. ... Delphi is still the best db tool in existence from what I can see. ... mail I receive from Borland, but I am already a convert). ... Oracle magazine, and there is no Borland advertising. ...
    (borland.public.delphi.non-technical)