A Look at the Internals of 'Tiered JIT Compilation' in .NET Core

Re:A Look at the Internals of 'Tiered JIT Compilation' in .N... by pjmlp on Tuesday December 19, 2017 @02:26AM (#15958405)

That point of view is outdated.

Hence Roslyn, .NET Native with VC++ backend, value types improvements and safer pointers in 7.x.

There are even plans to slowly move parts of the runtime from C++ into C#, now that .NET Native is a thing.

" So, in my view, the primary trend is moving our existing C++ codebase to C#. It makes us so much more efficient and enables a broader set of .NET developers to reason about the base platform more easily and also contribute"

https://www.infoq.com/articles/virtual-panel-dotnet-future

https://www.infoq.com/articles/high-performance-dotnet

[ Parent | on HN ]

Re:A Look at the Internals of 'Tiered JIT Compilation' in .N... by readittwice on Tuesday December 19, 2017 @05:37AM (#15959238)

Java seems to have a similar initiative called "Project Metropolis" to (re)write some stuff in Java instead of C++: http://mail.openjdk.java.net/pipermail/discuss/2017-Septembe...

[ Parent | on HN ]