Re: Why was win32 killed?

From: Bruce Jump (bjump_at_isa-inc.com)
Date: 10/03/03


Date: Fri, 3 Oct 2003 10:21:27 -0400

Very well said. My sentiments exactly. I had originally bugeted for this
release, but as it brings nothing new to the plate that I can use NOW (and
the keyword is "now"), I'll have to rethink things. Don't get me wrong
here, I will continue to use Delphi, there's no question on that.

Really was looking forward to a win32 + dotNet release though.

"Andrew" <nospam@nospam.com> wrote in message
news:3f7cb734@newsgroups.borland.com...

> Exactly. Is Borland going to repeat their history with Kylix? If so,
> they'll release Octane for thousands of dollars, and since it's only an
> experimental, sandbox environment for those of us who have to deal with
> an installed base of Win32 computers, the sales will be dismal, the
> excitement will die, and they'll have to change their price structure.
>
> Jim Gallagher

My thoughts exactly. I was looking forward to the combined product, as it
would allow my shop (15 developers) to trial and possibly migrate to .net at
our own leisurely pace and with low risk in terms of tool cost. Our
organisation is large and old, so change happens slowly here :-). In the
meantime we would have a productivity upgrade to our existing win32 tool in
the form of the new ide and evolved alm/mda support.

Now we are talking about an entirely separate product, whose purchase will
be difficult to justify if we just want to "play" with the new technology a
bit. I have already advised my manager that Borland will shortly begin
trying to sell us a "Delphi" product that we do not need, and that the one
we do need has yet to be announced. I have a feeling we are a fairly typical
Borland enterprise customer.

I sincerely hope that the next win32 release is combined with version 2 of
the .net release - I.e. that Octane as originally announced gets "finished"
once this interim .net only release is out the door. What they are
attempting to build (the combined ide) is ambitious and unprecedented, and I
hope they are given the chance to complete the task. Specifically, I hope
that Borland managers do not panic and blame the wrong things (e.g. Delphi
in general), when Delphi for .net version 1 sells, er,"modestly".

Finally, I find it ironic and sad that we newsgroupers have been hassling
Borland for so long to disclose their plans in advance. Now they have, and
of course the plans have changed at the last minute. I hope this doesnt put
them off the idea of being open with us in the future.

Cheers,
Andrew



Relevant Pages

  • Re: Moving from Delphi to C++
    ... "As we celebrate the 20th anniversary of Borland, ... Each release of Delphi has ... Octane will provide full support for both Windows 2003 and the ... of the VCL framework to enable the migration of existing Win32 ...
    (borland.public.delphi.non-technical)
  • Re: Borland, Let Delphi Live !
    ... they have ported their Win32 API to the platform and named it Win64 API. ... The only thing Im not confident about is creation of a Delphi for Win64 at any time soon. ... Thus I think that the moment there is a large enough population of 64 bit servers/desktops, Borland will ...
    (borland.public.delphi.non-technical)
  • Re: Thinking Clearly
    ... keep D7 for win32 and go VS for .Net. ... way for Borland to get more money from me (not me personally, ... option than to remain with Delphi; possibly adding VS if I had new ... They still support DOS ...
    (borland.public.delphi.non-technical)
  • Re: Delphi 2005 Win32 development stopped
    ... improve Win32 development or make a significantly better product for the end-user. ... Delphi, they wouldn't even merit a foot-note in marketting. ... someone from Borland or TeamB mentions for-in loops. ... and inherit all the bugs. ...
    (borland.public.delphi.non-technical)
  • Re: Future plans of Delphi for Win32
    ... > that Borland are not eccentric company. ... Plans yes, but if they reveal that plan and then has to change plans you ... this is how all business work. ... If Borland want to stop Delphi now - all Delphi community ...
    (borland.public.delphi.non-technical)