Re: A Programmer's proposal for the Delphi's roadmap
- From: "Nate Walker" <nate@xxxxxxxxxxxx>
- Date: Sat, 22 Apr 2006 18:26:39 -0500
I certainly hope my next set of video drivers aren't written and compiled
for .NET.
MS isn't *replacing* Win32 for systems-level programming, that would be
stupid.
Those types of applications are better off running outside of a VM. For
general
applications, yes they are "encouraging" .NET use because it does *ease*
programming
a lil bit and has a few inherent advantages over the Win32 model.
How the developer/user values this is up to them.
Nate.
"Brett Watters" <blwatters@xxxxxxx> wrote in message
news:444a88eb$1@xxxxxxxxxxxxxxxxxxxxxxxxx
Chau,
Unfortunately, Win32 isn't necessarily a market.
Win32 is an operating system level programming layer. One which
Microsoft is replacing.
1. Anything new and good will be in .NET. New interface, new
features, new database stuff, etc. will all be in .NET.
2. Components will be in .NET. Like it or not, VCL.NET removes
many of the advantages of .NET -- sharing components between
apps. It might be 'better', it might solve many of the .NET WinForm
problems, but it puts you in your own little field.
3. For Microsoft developers .NET is better. They don't see Delphi 7
vs. Delphi 2005. They see VB 7 vs. VB.NET. And things look great
for them. Everything which we took for granted, .NET solves (or
promises to solve) for VB and MS C users. Sharing of components,
single .EXE, a common framework underneath, no Active-X problems,
unicode, cross-language development, web-services, an integrated and
web development system, etc. And there are a lot of MS developers.
4. End users see better products out of the VB and C# folks and
the assume that .NET is better. They don't see "Missing .DLL errors",
they see fancier modern interfaces, the see common controls, they
see web-pages running at ten times the speed, they have less installation
nonsense, promises of web-services, etc. They then assume that anything
not .NET isn't as good as something .NET. You can't explain to them
that most of this Delphi Win/32 already did.
5. Microsoft is marketting the heck out of .NET. Like it or not, a
lot of people now see .NET as better. These are now your customers.
Given a .NET product and a Win/32 product... it doesn't matter that
the Delphi Win/32 might be better than the C# .NET app, they want
.NET.
6. Microsoft is promising all sorts of things under .NET. Folks now
see Win/32 as "old stuff" which won't have all the good new features
as .NET.
Borland had no choice but to go to .NET. They made a good (short-
term) solution to keep the Win32, but only as a stepping stone to the
.NET world. Eventually, the uses for a Win32 environment are going
to be pretty small. Eventually .NET will work and there will be little
reason not to develop for .NET exclusively.
Microsoft is banking on it. And Microsoft can change the playing
field to ensure that .NET wins.
.
- References:
- A Programmer's proposal for the Delphi's roadmap
- From: Chau Chee Yang
- Re: A Programmer's proposal for the Delphi's roadmap
- From: Brett Watters
- A Programmer's proposal for the Delphi's roadmap
- Prev by Date: Re: Delphi everywhere
- Next by Date: Re: A Programmer's proposal for the Delphi's roadmap
- Previous by thread: Re: A Programmer's proposal for the Delphi's roadmap
- Next by thread: Re: A Programmer's proposal for the Delphi's roadmap
- Index(es):
Relevant Pages
|
