Re: Thinking Clearly
- From: Tom Wilk <wilkt@xxxxxxxxxxx>
- Date: Tue, 04 Jul 2006 13:05:25 -0500
Michael Baytalsky wrote:
If you have no more need for Win32 support at all and need to start
.NET development *now*, then you would be making the only decision
available to you.
Exactly. Which means, keep D7 for win32 and go VS for .Net. No need to
purchase BDS 4.0, which means, no money to Borland, which means you're
However, if you want to maintain Win32 apps *and* move to .NET without
having to change your entire codebase to C# 2.0, then Delphi 2007
would more than likely be the ideal tool.
Same as above. I keep my D3-D5-D7 licenses and am very happy with them.
way for Borland to get more money from me (not me personally, but imaginary
developer like me) is to release DX which actually deliver something
for Win32. D2006 sort of does it, but is not polished enough yet.
At the same time, I don't care if it supports .Net. It's better if it
does not and works faster and more reliably and adds more Win32 features
instead. As a component vendor which I am, I hate to have to test my .Net
components with D2005-2006. Especially, 2005. It doesn't work exactly
as VS. You have to write separate design-time interfaces. That sucks!
Actually, I found that D2006 splash screen is the true reason I
never switched to D2006. Every time I start it, I curse the designer
who painted it black. Maybe I'm too sensitive, but I truly hate it.
It just blows my mind how they could have come up with a crap like this.
The nastiest thing is that it really reflects something that goes on
deep inside Borland and I don't like that reflection at all.
If I were still doing Win32 development, there is no other sensible
option than to remain with Delphi; possibly adding VS if I had new
.NET projects. The decision to move or not is based on whether you
want to 1. move to .NET, 2. rewrite all your Delphi code in C#.
The decision is not about moving, but whether one should invest into
new version of Delphi or not. If you keep promoting .Net, there's no
reason for us to invest into new Delphi, cause we'll be using VS for
| Long P.S. IMO, if you guys here at Borland won't stop promoting
| .Net you will end up in MS or under the bridge. You have got
| to be blind not to see that!
It is not so much a case of Borland promoting .NET, it is all about
Borland trying to keep up with providing tools to allow developers to
support as many platforms as possible and not get left behind.
IMO, they should only concentrate on Win32 and possibly on Linux and Mac.
That's still a niche (native portable development). If it is not, then
close the store. D7 is good enough. D2007 will not bring you return on
investment, unless you share the world be delivering something
breathtaking for Win32. Nobody cares for Delphi for DotNet. It's only
good for somebody to try DotNet before pitching Delphi.
| If DevCo wants to stay in business they must
| develop innovations that are not supported by .Net, better, then
| the ones in .Net, etc. If chasing MS eats up all the resources, then
| they need to stop chasing MS - that road leads to bankruptcy.
And if the future is really going to be one in which MS *ultimately*
intends to move the OS to .NET only ???
And drop all existing stuff? How's that possible? They still support DOS
etc. If they do so, then move to Linux or Mac, and MS will bury themselves
under the ruins of .Net.
I have no problem with the policy that MS will support Win32 for the
foreseeable future, but when users/clients get their hands on Vista
and see all the whizzy, whirly, visuals, etc and ask for apps that
look like that, how are Borland going to survive if they don't provide
tools to cope with those demands ?
You know better then me, that there will be native API to access all that
and it's only important for Borland to get that into some VCL+ as soon
as they can. MS will not be able to block anything as .Net only. You can
always be able to at least build a COM wrapper around .Net and it won't
be much slower, then .Net itself.
After all, you would have to convince the "nobody ever got fired for
using MS" mentality that a proprietary, non .NET tool is better; not
Well, I've managed to do so on every occasion so far. MS or non-MS is
not very important. At least it was not, when Borland is a public trading
company which does okey. You still work under Windows and support
you need to be supporting and can create state-of-art things much faster
then same things using MS tools. Nothing is going to change. .Net doesn't
provide any functionality, that you cannot have otherwise. In fact, it
takes away. When you talk about Java, at least you can see a benefit
of truly cross-platform development. In case of .Net, there's no benefit,
I love Delphi, I still think it's the best thing around and I refuse
to see any advantages in DotNet - anything they have there, can be
added to Delphi. I'm just very sorry to see DevCo wasting resources
chasing this marketing phantom.
HOW TRUE! I totally agree. .NET is a "marketing phantom" for Delphi
developers! DotNet is a great upgrade for the VB and MFC crowds, but a
step backwards for Windows GUI development.
- Prev by Date: Re: Evans Data Corp's IDE Scorecard on Delphi ...
- Next by Date: Re: Here's my bug report
- Previous by thread: Evans Data Corp's IDE Scorecard on Delphi ...
- Next by thread: Re: Thinking Clearly