"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

See this official MSDN article for reference...

Isn't it that we, Delphi users, claimed since decades?

Isn't it that an Open Source project like our little mORMot show?

And you can use "native UI controls" with Delphi or FPC, if you need to.

Do not trust the marketing sirens, even more if they are sponsored by billion dollar companies...
I would not trust the Embarcadero marketers by all means, but at least they were ahead of time and pushing a right argument here...
I'm less pleased by the NextGen roadmap, and performance loss of this model in its current implementation...

Feedback is welcome on our forum, as usual!

Synopse Open Source

"Native" means CPU-native... even Microsoft admits it!