Live data from Hacker News

Performance Improvements in .NET Core

blogs.msdn.microsoft.com

91–94 of 94 posts

Re: Performance Improvements in .NET Core

#91

Every time I try to get a quick feel of .NET on Linux, I allocate an hour to it and that hour is always spent wandering around various guides on microsoft.com and never getting anything done. There are terms like .NET Core, .NET Platform, .NET Framework, .NET SDK all mixed up on nearly every page, multiple versions of "Getting started" and "Quick start" guides, massive navigation menus and options on every page so yo…

Great points all, especially about the "simple downloadable .tar.gz." We will fix that. Until then, I wrote it up for you. https://www.hanselman.com/blog/TryingNETCoreOnLinuxWithJustA...

Thanks, Scott. This is another great example of Microsoft doing it right.

Re: Performance Improvements in .NET Core

#92
Owning and managing software business we develop using multiple technologies

Mobile objective c, swift, Android java, xamarin.net, phone gap

Web asp.net Mvc , php, java

Etc...

Using Asp.net Mvc requires using 3rd party ui libraries and Depends on size of team and experience in .net, usually we assign.net developers with at least 4 years experience in .net and front-end currently mvvm js libraries

If you starter in .net you have learning curve but this is reducing as technologies improve

Re: Performance Improvements in .NET Core

#93
post #37

for (int i = 0; i Shouldn't your compiler completely fold this? There are no side effects, it's single-threaded. This should take microseconds, not 86 milliseconds.

It's pretty tricky for the runtime to figure out that there are no side-effects, and that s.Min is not going to change, if the implementation behind it actually walks some nodes. Among other things, it would require it to prove that none of the walked nodes ever mutate anywhere else (don't forget that this includes backdoors like reflection).

Are there any notable languages that flat-out forbid reflection, or treat it as undefined behaviour?

Re: Performance Improvements in .NET Core

#94
post #86
post #82

Earlier quoted context omitted.

I played around with the binary-tree code. It's definitely because of Task (disabling the >= 17 heuristic doubles the memory usage). This should come way down with .Net Core 2.0 and ValueTask.

Does it come way down with .NET Core 2.0 Preview 1 ?

I have no idea. I've had upgrade issues with VS betas in the past, so I'm not willing to install it.
Post reply on HN