Re: TeamB, Borland, admit obvious

From: K. Sallee (nonomail_at_ecostats.com)
Date: 03/05/04 

Date: Fri, 05 Mar 2004 14:18:15 +0100

> On Fri, 5 Mar 2004 13:10:56 +0100, Hrvoje Brozovic <a.b@c.de> wrote:

> Conclusion: Borland statement in G directly contradicts
> Borland statement A and B

I fail to see the contradiction.

"Supported with minor source code changes" was all that was said said.

"Supported at the same level of optimal code", which you seem to imply was
said, was indeed not said. Nor do I see it being applied. Nor would I
ever assume such. It .Net, not win32, and just knowing what little I
still know about .Net you have to apply different logic to how things are
done. You *will* have to change some code to optimalize. But Borland
never implied you would not have to do so.

Borland just lets you compile your Win32 application now in .Net so you
can release a .Net version right away. No delays, no hangups, no hassle.
It gives you then time to learn .Net better and modify the application as
you go along from that point. There is no down time, from a developer's
perspective. That is pretty darn impressive.

Kevin 

-- 
Using M2, Opera's revolutionary e-mail client: http://www.opera.com/m2/

Relevant Pages

  • Re: Delphi 2005 Win32 development stopped
    ... For the past 5 years Win32 supports Unicode, but Borland won't ... > even consider supporting Unicode on Win32. ... Delphi, they wouldn't even merit a foot-note in marketting. ...
    (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: Latest information on Octane and Delphi
    ... > We are not ready, and will be no longer Delphi, nor Borland, customers. ... Win32 is still going to be around for awhile. ... Just because Borland didn't have enough time to include Win32 support by the ...
    (borland.public.delphi.non-technical)
  • Re: Why was win32 killed?
    ... here, I will continue to use Delphi, there's no question on that. ... Really was looking forward to a win32 + dotNet release though. ... Borland enterprise customer. ... Borland for so long to disclose their plans in advance. ...
    (borland.public.delphi.non-technical)
  • Re: Moving from Delphi to C++
    ... Ok, no mention of Win32, just more strong statements about .NET. ... >part of it and is even referenced in the second letter. ... >Borland acknowledged that they had originally stated there would be a Win32 ... >developed with Delphi for years to come and do plan to support and update the ...
    (borland.public.delphi.non-technical)