You are not logged in.
- Topics: Active | Unanswered
#1 2014-05-18 11:20:59
"Native" means CPU-native... even Microsoft admits it!
There were a lot of debate about what "native" was..
Especially for some great companies, you want to sell their compiler technologies...
For them, "native" is not CPU-native, but framework-native...
Even Microsoft claimed since the beginning of C# that the managed .Net model was faster, due to "optimized JIT or NGEN compilation"...
But even Microsoft is clearly changing its mind!
They switch to "Native" for their framework, especially when targeting mobile platforms!
So they officially switch to "Native":
For users of your apps, .NET Native offers these advantages:
-Fast execution times
-Consistently speedy startup times
-Low deployment and update costs
-Optimized app memory usage
Offline
#2 2014-05-18 15:53:46
- edwinsn
- Member
- Registered: 2010-07-02
- Posts: 1,218
Re: "Native" means CPU-native... even Microsoft admits it!
I noticed the .Net Native news few weeks ago, and it really got my attention. I'm quite sure it can be very compelling, at least to me, if it finally supports the entire .Net framework for desktop, given the fact that Visual Studio and the .Net framework, both are so far ahead of the Delphi IDE and VCL, and c# is a nice language, so if the speed thing can be fixed, it'll be amazing. But who knows if MS will finally get to that point.
Delphi XE4 Pro on Windows 7 64bit.
Lazarus trunk built with fpcupdelux on Windows with cross-compile for Linux 64bit.
Offline
#3 2014-05-18 16:27:19
- ComingNine
- Member
- Registered: 2010-07-29
- Posts: 294
Re: "Native" means CPU-native... even Microsoft admits it!
IMHO .Net Native uses normal GC, which is one of the pains....
Offline