Re: Thinking Clearly



I.P. Nichols wrote:
The battle for the .NET space isn't your fathers battle for the Win32 space!

Agreed, but my father wouldn't know Win32 from outer space. ;)

It only has to do sufficiently well in any space.

Regardless of what one thinks "win" means, there can be little doubt that if
DevCo's Delphi is to be viable in the future .NET space it must attract new
users to generate revenues to justify the outlay of resources in it's .NET
products. There are those who believe that VCL.NET (plus) ECO will not be
made sufficiently attractive to lure enough new users into the Delphi camp.

Agreed. But IMO, they aren't sufficiently attractive to even maintain
Delphi's customer base as they move towards .NET.

I have always thought that the BDS and VCL.NET was an absolutely brilliant
strategy necessary to bring calm and avoid rebellion in the loyal Delphi
camp

Eh...they needed a .NET story that involved Delphi for sure. And I'm
pretty certain that any story could have been sold to the Delphi
community. Even one that broke backward compatibility to large degree
or a mixed-mode compiler.

but it would increasingly become problematic as .NET evolved and
morphed into what it will be with .NET 3.0. From what I know today it does
seem my concern was justified...

I'm not sure if it's the evolution of .NET or merely the scope and the
overall quality of it. IMO, DevCo can't compete from a resource
perspective, but yet with Delphi for .NET and VCL.NET the strategy is
working harder rather than smarter.

--
Brian Moelk
Brain Endeavor LLC
bmoelk@xxxxxxxxxxxxxxxxxxxxxxxxxxxx
.



Relevant Pages

  • Re: Thinking Clearly
    ... I inferred it from "But IMO, there is no tangible benefit to moving Delphi ... Win32 code forward to .NET. ... Sometimes good theories don't pan out, particularly when normal market ...
    (borland.public.delphi.non-technical)
  • Re: The alternative Delphi roadmap to success
    ... How do you interpret Borland going out of it should it be commercially viable? ... If MS had decided to use Pascal instead of C, for Windows, we wouldn't have that number of patches and hotfixes, IMO. ... Without a chance to demonstrate the advantages of Delphi, over other languages, where should new Delphi users come from? ... The development could be simplified, if Delphi.NET would become a language module in the Microsoft VisualStudio, instead of suffering from an poorly documented language and IDE of it's own. ...
    (borland.public.delphi.non-technical)
  • Re: The Delphi Survey
    ... IMO, Delphi has yet to break out successfully from it's rich GUI ... really a new OS platform of any significance. ... There are essentially 4 competitive strategies: price, differentiation, ...
    (borland.public.delphi.non-technical)
  • Re: Definition of outdated...
    ... That is one of my main topics regarding Delphi. ... Its imo where Delphi would ... Map etc and no generics support to ... There are loads more functionality in Java for example for this stuff, ...
    (borland.public.delphi.non-technical)
  • Re: Why arent you upgrading?
    ... IMO, ... I don't think that DevCo should be afraid of making and keeping ... Delphi different. ... Native code has its niche, managed code has its niche, ...
    (borland.public.delphi.non-technical)