My boss and our lead programmer went ot some MS thing in Sydney a few months
back on .Net etc.
They came back somewhat unimpressed and have pretty much decided against it
in favor of Java and Delphi solutions (YAY)...hence why we are looking to go
to BorCon....
The one major thing that put them off what the hardware requirements that
are needed....its a hell of a size for a runtime...hahaha MS have done
themselves proud in the bloat department :-) Maybe they got paid a bonus
that was perportional to the bloat factor......
Most people I have heard of that have seen C# are impressed (as has been
indicated in other emails) I myself have only seen it not used it.
(thats my 2c worth)
Jeremy Coulter
-----Original Message-----
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]]On Behalf Of Max Nilson
Sent: Thursday, 20 September 2001 16:13
To: Multiple recipients of list offtopic
Subject: RE: [DUG-OFFTOPIC]: Visual Studio .net Beta 2
Grant Black asked the interesting question:
> Perhaps I have missed the point of .NET, (other than normal MS
> world domination plans) but why would we want a Delphi.NET?
> For that matter, why not just use Delphi, Java instead of yet
> another language like C#?
and I thought I should pitch a few opinions into the stew.
Why have Delphi.NET and why use it? I can think of a few issues that would
make this a nice tool to have available:
1. Marketing and Survival. .NET is a direct competitor to the Delphi
product, and Borland must maintain mind share and use share to remain in
existance for another decade or two.
2. Portability part 1. In theory (and if done right) your Delphi.NET
application could be ported into Kylix with minimal changes. A nice cross
platform trick that would make MS seriously grumpy 8-) Also means that a
slow Delphi.NET app could be recompiled into Delphi native code for a speed
boost.
3. Portability part 2. A CLR based Delphi would, in theory, allow
development for future 64 bit MS operatings systems with little effort on
Borlands part. Either Borland does this or they must develop their own
Itanium compiler technology to provide a native 64 bit Delphi.
4. Size. .NET applications will be tiny as they can assume a standard run
time environment. This means your Delphi.NET application willk not need to
carry around the equivalent of the VCL with it. Unfortunately this not a
good reason to use Delphi.NET as opposed to C# or other CLR products.
5. Compatibility. MS has the annoying habit of making new services dependant
on their latest environment. If Delphi wants to stay up with the play it
would be faster to have Delphi.NET talking to the built in MS API's rather
than jumping through hoops to get raw Delphi talking to things. For old
examples see MAPI and TAPI programming issues.
Unfortunately is a huge down side to this product, namely it would dilute
Delphi's unique nature and make it one of a breed. Plus it would make Delphi
reliant on .NET as a platform.
So either you think .NET is goiong to go into the history pages of main
stream development (like Java is threatening to do) and Delphi should ignore
it, or its the platform of the 21st Century and is going to replace Win32 as
the dominant programming environment and Borland must follow along. Either
way you pretty much answer what Borland must do to continue opening new
markets with Delphi.
Cheers, Max.
---------------------------------------------------------------------------
New Zealand Delphi Users group - Offtopic List - [EMAIL PROTECTED]
Website: http://www.delphi.org.nz
To UnSub, send email to: [EMAIL PROTECTED]
with body of "unsubscribe offtopic"
Web Archive at: http://www.mail-archive.com/offtopic%40delphi.org.nz/
---------------------------------------------------------------------------
New Zealand Delphi Users group - Offtopic List - [EMAIL PROTECTED]
Website: http://www.delphi.org.nz
To UnSub, send email to: [EMAIL PROTECTED]
with body of "unsubscribe offtopic"
Web Archive at: http://www.mail-archive.com/offtopic%40delphi.org.nz/
