Re: compiled Delphi.NET?
From: Anthony Carrabino (anthonyc_at_vistasoftware.com)
Date: 06/08/04
- Previous message: Dennis Landi: "A Tale of Two Memory Managers (long)"
- In reply to: Paul Dolen: "Re: compiled Delphi.NET?"
- Next in thread: Mike Swaim: "Re: compiled Delphi.NET?"
- Reply: Mike Swaim: "Re: compiled Delphi.NET?"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Date: Tue, 8 Jun 2004 00:13:36 -0700
I was at PDC 2003 and spoke with Jose Blakely, SQL Server Architect
after a "Hosting the CLR" presentation. I asked him about SQL Server
becoming fully managed at some point, he said it will not happen any
time soon (actually years) simply because there are millions of lines
of code to convert. He said that SQL Server is a mini-OS.
The presentation was on hosting the CLR, during which the MS panel
stated that many of new features in the CLR 2.0 were being added
specifically to give SQL Server more efficiency in hosting the CLR.
SQL Server is the 3rd most profitable software product at Microsoft,
so it carries serious weight. IMO, this Managed C++ stuff, with the
ability to generate unmanaged code (which, is there today) is just
another in-house need by the SQL Server team to beef up their own
tools for making SQL Server better. I wouldn't read too much into
this divergence in managed .NET architecture purity as the way
to do it.
The crux of .NET is managed code, otherwise, what's the point?
Microsoft will push security (i.e.. managed code) super hard to sell
Longhorn. And yes, 64-bit computing. Over the next 24-36 months,
i predict we will see the following (all of which designed to sell
Longhorn):
- a continued emphasis by MS for developers to write managed code
- the need for end-users to run managed code (i.e.. security)
- 64-bit computing will be pushed along with Longhorn (Intel and AMD
will want this, hence the quick about face by Intel)
- less emphasis on Pocket PC OS because new micro-pcs
(the size of PDAs) are running full blown XP, which seriously hurts
the Pocket PC growth. So one less platform to worry about.
Side comment about 64-bit: maybe IL code will be go 64-bit without
needing changes. I heard rumors about this, but I'm not a compiler guy,
so i'm over my head on this last point.
-- Anthony Carrabino www.vistadb.net "Paul Dolen" <nospam@nowhere.com> wrote in message news:mq71c0pr3o860tflaq2p2sr4hql0hl1jg4@4ax.com... > > The next version of VC++ does indeed seem to have performance > >improvements in its unmanaged compiler. I remain to be convinced that > >IL produced with Managed C++ will be "better" than IL produced with C# > >or Delphi. I very much doubt that will be the case. > > What I'm getting from the C++ group is that managed C++ is dead or > will be in the next version. Managed C++ produces IL which nobody > wants. If they want IL, they want C# or VB or Delphi. But, the next > version of VC++ will allow .NET access from real compiled C++. Which > is why I'm asking, might that not be a better route for Delphi also? > Maybe? >
- Previous message: Dennis Landi: "A Tale of Two Memory Managers (long)"
- In reply to: Paul Dolen: "Re: compiled Delphi.NET?"
- Next in thread: Mike Swaim: "Re: compiled Delphi.NET?"
- Reply: Mike Swaim: "Re: compiled Delphi.NET?"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Relevant Pages
|