News for hackers. Stuff that matters.
Re:Performance Improvements in .NET Core by ksubedi on Wednesday June 07, 2017 @01:48PM (#14508380)
As .net core is a full rewrite, all these optimizations are .net core specific, so porting them isn't going to be a easy thing.
Re:Performance Improvements in .NET Core by paavohtl on Wednesday June 07, 2017 @03:24PM (#14509163)
.NET Core is not a rewrite in any way. It's the same runtime with the same GC and JIT, same language compilers and mostly the same standard library. It has just been stripped down by removing deprecated features (such as code sandboxing / partial trust) and made support non-Windows platforms.

You might have confused it with ASP.NET Core, the web development framework, which is a full rewrite.

Re:Performance Improvements in .NET Core by T-hawk on Wednesday June 07, 2017 @05:56PM (#14510182)
If a developer confuses .NET Core and ASP.NET Core, is that a fault of the developer, or of Microsoft's nomenclature?
Re:Performance Improvements in .NET Core by ksubedi on Wednesday June 07, 2017 @09:44PM (#14511269)
You are right, i was confusing asp.net core with .net core.
Re:Performance Improvements in .NET Core by yawgmoth on Wednesday June 07, 2017 @01:55PM (#14508457)
Hopefully these optimizations are for a particular version of .NET Standard and will see themselves in both .NET Framework and .NET Core.
Re:Performance Improvements in .NET Core by jacobparker on Wednesday June 07, 2017 @02:03PM (#14508520)
Skimming, but it doesn't look like these optimizations are relevant to .NET standard (which is a formal specification of a set of APIs - not a particular implementation.)
Re:Performance Improvements in .NET Core by runfaster2000 on Wednesday June 07, 2017 @03:07PM (#14509018)
Correct. Performance improvements are out of the scope of the standard. Much like how the HTML spec doesn't tell Google and Microsoft how fast their browsers need to work.