Re: New Delphi roadmap is coming: NO UNICODE PLEASE!

I.P. Nichols wrote:

"Ingvar Nilsen" wrote:
I.P. Nichols wrote:

Rather than just keeping existing developers the other side of the
coin is how to attract new developers. Even under the best of
circumstances there will always be attrition and to be vibrant
CodeGear absolutly needs new customers and the more the better.

Applause
This is crucial IMO, and here is why CodeGear cannot ignore .Net

to
attract a significant number of new .NET customers IMO they must go
head-to-head against Visual Studio

No, see below

and that's both damn risky and
outrageously resource intensive.

And probably impossible

Some other avenue is much more
likely to prove rewarding than pouring scarce resources into a
bottomless pit chasing after rapidly evolving .NET technology.

It depends on what you do with .Net. Who has said making a VS clone is
the only way to go? What about a VS plug-in? Ok, I hear it coming, "MS
doesnt allow plug-in made by IDE makers". But Together for Visual
Studio is a VS plug-in, and is sold by Borland, who owns CodeGear,
"wholly" to boot.

The first step IMO for everyone is to replace the ubiquitous mindset
that Delphi is and should be a VS competitor. If it has been, it cannot
be in the future, provided Delphi does not move a few stairs and steps
up and becomes a platform like VS is now.

Delphi has to be Delphi IMO, and that does not contradict Delphi doing
..Net, in one way or another.
Whaddoyuthink?

--
Ingvar Nilsen

Brand New Web Site! Free Delphi Tool:
http://www.ingvarius.com
.

Relevant Pages

  • Re: So Long and Thanks for all the Fish!
    ... IMO, new features aren't enough. ... beyond the scope of what CodeGear is capable and committed to doing. ... Beyond that, IMO, Delphi being Windows-only and primarily ...
    (borland.public.delphi.non-technical)
  • Re: ECO, Delphi, Codegear, and CapableObjects (Delphi for VS!)
    ... but you posed the question "what can't you do with Delphi ... IMO, you really don't want to hear or acknowledge ... CodeGear doesn't define the "problem", ... on providing "solutions" to Delphi's existing shortcomings. ...
    (borland.public.delphi.non-technical)
  • Re: Delphi and the .Net platform
    ... IMO, this is not going to work. ... I suppose those same people would fear distributing a free Delphi ... They will fear it until CodeGear tell them not to. ... able to deploy a full server image without worrying about any linux ...
    (borland.public.delphi.non-technical)
  • Re: I have seen some fat client Dot Net apps
    ... OSX is more important where Delphi traditionally shines. ... and this is where the focus for the Delphi developer should be IMO. ... but the main point here is that CodeGear and more specifically ... The reason why I'm glum about the future of Delphi is primarily because ...
    (borland.public.delphi.non-technical)
  • Re: Attention doomsayers
    ... I am very worried where Code Gear, and more importantly Delphi will be in 3 years. ... One, is to seed the market with low to zero costs (not sure CodeGear can afford to do this), The Turbos are a good idea and can aid with this introduction. ... start making deals with third party vendors to create plugins for their environments. ... MS apps are at the point with VS 2008, ...
    (borland.public.delphi.non-technical)