Re: Delphi - does catastrophe loom ? (long)
- From: "Tim Anderson" <Timjand@xxxxxxxxxxxxx>
- Date: Tue, 12 Apr 2005 08:16:41 +0100
"Mat Ballard" <mat@xxxxxxxxxxxxx> wrote in message
news:425b26a7$1@xxxxxxxxxxxxxxxxxxxxxxxxx
> I believe that .NET has been grossly over-hyped, in typical Microsoft
> fashion. While the original intent seemed for it to be a Java replacement,
> it is now pushed as the general programming language for future versions
> of Windows. However, recent posts on its performance have confirmed its
> Java-like performance (memory x 5, speed x 0.02-0.2), which makes it
> unsuitable for general desktop applications.
Hmmm, the speed difference you quote is not typical, thus not ideal for
supporting your argument.
Your statement about unsuitability for desktop apps also seems to be
undermined by the popularity of a number of apps written with the .NET
Framework. For example RSS clients - RSS Bandit, SharpReader, Omea Reader,
others too.
Is .NET suitable for all desktop apps? No. Is .NET unsuitable for any
desktop apps? No.
> On the other hand, how good a competitor will it be for Java given the
> amount of baggage needed
Since you are concerned about the future of Delphi, you should look at the
business case as well as the technical case.
No-one doubts that Win32/Win64 has a future. However, even before .NET,
Win32 programming was in decline. Sun cut off the Java route; Microsoft had
little choice other than to implement its own Java-like framework. Automatic
memory management, component-oriented, proper built-in security, thought-out
versioning, new languages which are more productive than VB/C++, mobile
device support, new framework for web apps, etc etc.
Ignoring .NET in Delphi doesn't look like a viable business option.
Bear in mind though that unlike VB.NET, C#, Delphi still does Win32. Will it
ever do Win64? No idea, but that route is not closed.
Borland did have another option. Forget .NET and go for cross-platform. In
fact, at one time that looked like the strategy (Kylix). Kylix was a flop in
the market, for whatever reason. Perhaps it should have persevered. I think
Borland simply accepted that Delphi is primarily a Windows tool; it would be
nice to see Linux and Mac support come back via Mono at some future time.
> Unfortunately .NET (especially VCL.NET) is a 32-bit technology that was
> not written to exploit parallelism to the fullest.
Note that .NET 2.0 has a 64-bit version. I agree VCL.NET will have problems
as it is full of Win32 interop. Could be fixed though. But note that Delphi
also supports WinForms. The answer is to design your apps with nice
separation between GUI and logic.
> Guess who has released a 64-bit compiler ? Our good friends at Microsoft -
> who have been ramming .NET down everyone else's throat.
>
> It's a bit like the old OS/2 debacle: Microsoft conned lots of people into
> investing in one technology (OS/2), then brought out a different one
> (Win95 + NT).
You are saying that .NET is a kind of distraction marketing while Microsoft
really focuses on Win64? That seems fanciful; I see no evidence for it. I am
sure there are internal debates within Microsoft that echo those on this
newsgroup, about .NET vs native code. However I also see substantial
commitment to .NET and key apps that use it - SQL Server 2005, Sharepoint,
BizTalk etc
> It has been said that Borland invested several million dollars in research
> into 64-bit technology.
> Well, it still seems to be off Borland's agenda.
I doubt it is off the agenda. I imagine it is, as ever, a question of
priorities. Undoubtedly 64-bit native code Delphi is desirable.
> Prediction:
> ***********
> If Borland sticks to just .NET its market share will plummet because .NET
> applications have severe performance problems that future hardware
> developments will not solve.
Overstated.
> Delphi will become a niche product then die out.
It is *already* a niche product.
> Microsoft will clean up the compiler market with a 64-bit product that
> also does .NET if you really insist on it.
Here is the UK, .NET already appears to be very widely used for programming
business apps for the Microsoft platform. I don't see that changing.
> Gets down on knees and begs:
> ****************************
> That Borland's Marketing people pull their finger's out: the market is
> _HUGE_.
For years, Delphi was the best way to program windows apps - it remained a
niche product. No doubt lots of reasons, but this isn't going to be fixed
simply by a 64-bit native code edition.
> Let your technical people show that they are the best !
Fully agreed.
Tim
..NET Pros and Cons
http://www.itwriting.com/phorum/list.php?f=6
.
- Follow-Ups:
- Re: Delphi - does catastrophe loom ? (long)
- From: Nick Hodges [TeamB]
- Re: Delphi - does catastrophe loom ? (long)
- From: Dave Jewell
- Re: Delphi - does catastrophe loom ? (long)
- From: Will DeWitt Jr.
- Re: Delphi - does catastrophe loom ? (long)
- From: Eric Grange
- Re: Delphi - does catastrophe loom ? (long)
- References:
- Delphi - does catastrophe loom ? (long)
- From: Mat Ballard
- Delphi - does catastrophe loom ? (long)
- Prev by Date: Re: Now it's more than a month since update 2, still no update 3.
- Next by Date: Re: Delphi 2005 Update 2 german
- Previous by thread: Re: Delphi - does catastrophe loom ? (long)
- Next by thread: Re: Delphi - does catastrophe loom ? (long)
- Index(es):
Relevant Pages
|