In article <46e64137$
XXXX@XXXXX.COM >, Frank J wrote:
Quote
>Are you implying that VCL is Object Pascal-based it's somehow slow?
>That MFC makes things fast?
I'm implying that the VCL Framework is slower than MFC.
One would expect it to be so, as it provides a higher level of abstraction
than MFC, and runs on top of the same set of platform APIs. MFC is a
thinner layer (which is both an advantage and a curse) and so should be
expected to be add less execution overhead.
Whether that difference in speed is even noticeable in a typical
application on a typical user's PC is another matter.
This has nothing to do with VCL being in Pascal, though.
Quote
Should be rephrased from :
"How can the VCL benefit from the new processor architecture like .NET?"
to
"How can the VCL benefit from the new processor architecture like .NET
can"?
Actually, to a very great extent .NET can't. To take full advantage of a
new processor architecture you have to write native code that takes
advantages of -- and makes best use of -- its new features.
It's true that once you have implemented the .NET/Mono runtime on a new
architecture a .NET application will run on that platform without change,
so the application is protected from obsolescence by the abstract nature of
the .NET platform ... that's not really "taking advantage of" the platform,
though, I'd describe that as "being isolated from progress". The
application can only take advantage of the architecture of the .NET virtual
machine; it can't see the new underlying hardware architecture to make use
of it. Yes, the runtime itself can take advantage of the new hardware
platform, internally, but there is a limit to the extent that it can make
the features of that platform available to its client apps.
Cheers,
Daniel.