Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Performance Improvements in .NET Core

blogs.msdn.microsoft.com

Post reply on HN
Print view View original

51–60 of 94 posts

Re: Performance Improvements in .NET Core

#51

Post by jacques_chester »

runfaster2000 wrote: post #49
jacques_chester wrote: post #46

Earlier quoted context omitted.

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

Thankyou! I will ping my colleagues tomorrow.

Re: Performance Improvements in .NET Core

#52

Post by revelation »

rubyn00bie wrote: post #50
old-gregg wrote: post #14

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 t…

It takes about 5 minutes to set up the dotnet CLI tools and get a "Hello World".

If you don't even want to spend that you can install Visual Studio and .NET Core stuff will just work out of the box, as is customary for VS.

Versioning and documentation is a mess, but neither you nor the grandparent seem to have actually made the minimal time investment necessary to even encounter those problems.

Re: Performance Improvements in .NET Core

#56

Post by runfaster2000 »

bitmapbrother wrote: post #26

What's up with the memory consumption of C# .Net Core? It looks like it has dethroned Java as the memory bloat champion. http://benchmarksgame.alioth.debian.org/u64q/csharp.html

We haven't spent much time with those benchmarks. We looked at a couple of them and believe that there are better ways to write them in C# and get better results. That's not FUD but our findings.

This is a great community activity. Clearly, the community is more than capable of performance enhancements, based on the improvements they have made in the product.

If people start improving the C# benchmarks, please file an issue on dotnet/core to get feedback and some cred. We may do another blog post on that if there is some gravity around the activity.

Re: Performance Improvements in .NET Core

#57

Post by rubyn00bie »

revelation wrote: post #52
rubyn00bie wrote: post #50

Earlier quoted context omitted.

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 t…

It takes about 5 minutes to set up the dotnet CLI tools and get a "Hello World". If you don't even want to spend that you can install Visual Studio and .NET Core stuff will just work out of the box, as is customary for VS. Versioning and documentation is a mess, but neither you nor the grandparent seem to have actually made the minimal time investment necessary to even encounter those problems.

Yeah the problem isn't "hello world." It never is, it's building something with the tooling that works cross platform or that can be deployed to the platforms I want to target. That's much more than "hello world" and the important part.

Perhaps you could make a useful comment next time instead of something plainly not?

Re: Performance Improvements in .NET Core

#58

Post by jacques_chester »

runfaster2000 wrote: post #53
jacques_chester wrote: post #51

Earlier quoted context omitted.

Thankyou! I will ping my colleagues tomorrow.

BTW: Your friends can also contact me -> rlander@ms

The thankyous keep rolling. I also remembered I can point you at the Slack instance where they live -- https://slack.cloudfoundry.org/, in the #buildpacks channel.

Re: Performance Improvements in .NET Core

#59

Post by mistermann »

revelation wrote: post #52
rubyn00bie wrote: post #50

Earlier quoted context omitted.

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 t…

It takes about 5 minutes to set up the dotnet CLI tools and get a "Hello World". If you don't even want to spend that you can install Visual Studio and .NET Core stuff will just work out of the box, as is customary for VS. Versioning and documentation is a mess, but neither you nor the grandparent seem to have actually made the minimal time investment necessary to even encounter those problems.

> Versioning and documentation is a mess, but neither you nor the grandparent seem to have actually made the minimal time investment necessary to even encounter those problems.

This is Microsoft's fault, not these guys, and it has pissed me off so many times over the years.

I always use the analogy that Microsoft builds these gigantic, beautiful mansions, but then to get to them you have to find the secret path that's covered in weeds.

A slightly different topic, but very much along the same theme:

http://i.imgur.com/KiA3SKv.png

What a mess! I want SSMS, do I even have it installed anymore? How do I clean this up without spending 6 hours (because I know something's going to go wrong during the uninstall)?

Re: Performance Improvements in .NET Core

#60

Post by spronkey »

rubyn00bie wrote: post #50
old-gregg wrote: post #14

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 t…

Definitely seconded. Do a bit of .NET (non-core) maintenance too, so it's not like I'm completely unfamiliar with it.

Though, maybe legacy knowledge isn't helping...

Post reply on HN