Live data from Hacker News

Performance Improvements in .NET Core

blogs.msdn.microsoft.com

41–50 of 94 posts

Re: Performance Improvements in .NET Core

#41

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…

It's very easy.

Re: Performance Improvements in .NET Core

#42
post #39

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…

https://www.microsoft.com/net/core#linuxredhat I see. 4 steps too hard. I bet you're a Go code monkey?

Actually the instructions for Debian are the best: download the tarball, adjust $PATH and go: https://www.microsoft.com/net/core#linuxdebian

But I went "ubuntu" route and bailed, looking for a simple tarball.

Re: Performance Improvements in .NET Core

#43
post #4

Earlier quoted context omitted.

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.

.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.

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

#44

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…

This is my EXACT experience. It's crazy how similar both of our experiences were. Crazy amounts of fury navigating the Microsoft docs.

Re: Performance Improvements in .NET Core

#45

Earlier quoted context omitted.

> I still haven't quite grasped the relation between core and the full framework when it comes to fixes like this being merged into the full framework. From what I can tell, from following the CoreCLR repo ( https://github.com/dotnet/coreclr ), it's changed over time. In the beginning the sources of the 2 were more closely tied, changes were (automatically?) copied over. Now it seems like it's more ad-hoc, done as an…

If you take a look as these issues, it's clear that they're happy to make the source code very different, i.e. hard/impossible for changes to be automatically ported across. Just look at how much .NET Framework (Desktop) code they removed from CoreCLR earlier this year! - https://github.com/dotnet/coreclr/issues/8857 - https://github.com/dotnet/coreclr/issues/8763 - https://github.com/dotnet/coreclr/issues/4651 - htt…

> Just look at how much .NET Framework (Desktop) code they removed from CoreCLR earlier this year!

Perhaps I'm missing something but wouldn't removing Windows specific code from a now cross platform runtime be the obvious thing to do?

Re: Performance Improvements in .NET Core

#46

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…

Point taken. We have some improvements to make on this front.

Speaking of names and versions -- while working on Cloud Foundry Buildpacks we frequently turned our brains into pretzels trying to manage what components were versioned how. We even had custom logic to parse a YAML file where we maintained a mapping to keep things straight.

Especially since some components embedded different versions of other components.

I don't know if the situation has improved since I rotated off, but a bog-ordinary semver scheme would've saved a world of pain.

Failing that, a single page with components (SDK? Runtime?) and available version numbers that gets updated.

Because we mostly wound up working what was what from forensic readings of scattered blog posts, Github release and I think comments on Github issues.

In any case, I am sure the team would be glad to give you feedback on their experiences since then -- my email is in my profile if want me to pass anything along.

Re: Performance Improvements in .NET Core

#47

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…

Yo! Great point! In fact current dotnet core site was hugely inspired by golang one (IMO). Just take a look: http://dot.net/ There's also a great 20 lesson in-browser interactive tutorial (there's also F# and VB version!): https://www.microsoft.com/net/tutorials/csharp/getting-start... I'd also like to stay on this cool dot.net domain though, microsoft.com might scare people.

Re: Performance Improvements in .NET Core

#48

Always interesting timing by technology companies. Here's a post to developers by Microsoft the day AFTER Apple's State of the Union presentation to developers. Microsoft touting performance improvements the day after Apple amps up performance on pretty much every aspect of the Apple developers infrastructure (Xcode, Swift, APIs, processor and GPU utilization, etc). Must be a coincidence...

What difference does it make when .NET Core is cross platform anyway?

Re: Performance Improvements in .NET Core

#49

Earlier quoted context omitted.

Point taken. We have some improvements to make on this front.

Speaking of names and versions -- while working on Cloud Foundry Buildpacks we frequently turned our brains into pretzels trying to manage what components were versioned how. We even had custom logic to parse a YAML file where we maintained a mapping to keep things straight. Especially since some components embedded different versions of other components. I don't know if the situation has improved since I rotated off…

See: https://github.com/dotnet/designs/issues/2

Re: Performance Improvements in .NET Core

#50

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…

My experience has largely been the same, the whole mono, xamarin, vs studio, etc of tooling (whatever it all is) is a tragedy of good technology made useless. The licensing, tooling, and runtimes are such a mess I give up before I begin. There needs to be one canonical way to do things on every platform, this "band-aid" approach might've worked when you first open sourced but surely no longer does the job.

I'd love to use .NET but the overhead of getting started isn't worth it when I can use any number of other truly free languages/platforms that are much easier to understand. And are truly cross platform because they have been so for years.

For reference languages I use regularly or on occasion which don't suffer from any degree of the issues .NET has: ruby, swift, elixir, java, scala, JavaScript, and Elm.

CLR and .NET seem very awesome but so far have turned me off in a big way. Please fix <3

Post reply on HN