Live data from Hacker News

Performance Improvements in .NET 6

devblogs.microsoft.com

21–30 of 256 posts

Re: Performance Improvements in .NET 6

#21

My favorite part of dotnet 6 is the focus on hot reloading not mentioned here. Being able to work on a webapp that rapidly reloads in under a second is huge. It allows me to maintain the state of flow as I'm bringing something to life. I had a unique use case wherein I had a separate worker thread that also needed reloading with the hotreload. I was able to hook into the hot reloading via "[assembly: System.Reflectio…

The thing I like the best with dotnet (core) is how great is the cross platform support (for console and web applications). I use macOS most of the time, to build Linux containers and this works perfectly. I recently found a bug in the SDK... which impacts Windows only. Other OS than Windows are really supported.

Re: Performance Improvements in .NET 6

#22

My favorite part of dotnet 6 is the focus on hot reloading not mentioned here. Being able to work on a webapp that rapidly reloads in under a second is huge. It allows me to maintain the state of flow as I'm bringing something to life. I had a unique use case wherein I had a separate worker thread that also needed reloading with the hotreload. I was able to hook into the hot reloading via "[assembly: System.Reflectio…

> My favorite part of dotnet 6 is the focus on hot reloading not mentioned here

Does this work, for example, to reload method changes and so on? I miss this coming from JVM.

Re: Performance Improvements in .NET 6

#23
post #11
post #5

Making JIT 4% (or whatever) faster is cool but it would probably have higher ROI for the .NET ecosystem if Microsoft assigned some of these high caliber people to instead work on improving or simply rewriting some of the atrocious open source libraries that are available. Would you rather have an A language/runtime with a D open source ecosystem or a B for both?

What are some of the libraries you're thinking of?

I'd like to see them to roll their own identity platform after IdentityServer went close source.

Re: Performance Improvements in .NET 6

#24

My favorite part of dotnet 6 is the focus on hot reloading not mentioned here. Being able to work on a webapp that rapidly reloads in under a second is huge. It allows me to maintain the state of flow as I'm bringing something to life. I had a unique use case wherein I had a separate worker thread that also needed reloading with the hotreload. I was able to hook into the hot reloading via "[assembly: System.Reflectio…

> My favorite part of dotnet 6 is the focus on hot reloading not mentioned here Does this work, for example, to reload method changes and so on? I miss this coming from JVM.

It really works!

"dotnet watch" and go. It watches your C# files for changes and reloads when it notices on save.

I use VSCode not visual studio which has some deeper integrations there I guess. But it's still fine.

It's only available in 6, though, as far as I know for real sub-second hot reloads. As it's a preview release right now, it's not as fun to set up but it's not too bad.

5 and below has reloading on code change that isn't quite instant (takes maybe a few seconds) but still works with the same command.

Re: Performance Improvements in .NET 6

#25
post #9

For large enterprises, that use AWS / GCE / Azure, these improvements directly translate into huge savings in server capacity. I have always loved .NET and it keeps getting better and better. They have shown remarkable flexibility to throw away ideas that don't work and have modernized. A large part of that is due to active involvement of the community. This could be a new model moving forwards, a software worlds equ…

I’m thorn on that. As someone who has had intermittent periods of .NET, it’s a complete mess every time I’ve come back after a couple of years off and figuring out what new APIs are the new thing to use, which have been deprecated and when looking for a solution of something involving e.g. configuring stuff in the web server request handing stack it’s a real confusing mess.

Docs of course aren’t all up to date and are some times contradictory. Maybe it's better today but I've had plenty of 404s on official docs as well.

It’s way worse than React in this regard (if not only by its sheer size and larger scope)

The rapid changing allows them to do good stuff like you say, but it’s like the only way to write modern .NET properly is to have throughly read every release notes since about v4....

Re: Performance Improvements in .NET 6

#27
post #4

Impressive work (and blog post)! Somebody noticing real world performance impact after upgrading to latest .NET Core versions?

Saw impressive performance jumps on a full Core 3.0 -> Net 5 upgrade in 2020.. looking forward to testing out 6 (post preview).

Re: Performance Improvements in .NET 6

#28

Where should someone start if they wanted to get familiar and proficient with .NET?

Check out F#, the bastardized yet legitimate child of MSFT.

If you like functional languages or would like to try it, give it a whirl!

https://dotnet.microsoft.com/learn/languages/fsharp-hello-wo...

If you use vscode, highly suggest to use Ionide extension. You’ll be quickly amazed at how smooth it all works.

Re: Performance Improvements in .NET 6

#29
post #13

Where should someone start if they wanted to get familiar and proficient with .NET?

For somebody who already knows how to program, and enjoys getting a comprehensive data dump, C# 9.0 In a Nutshell.

Yes, it's a truly fantastic book for beginners and veterans alike. It's too big for most people to read cover to cover, but as a reference book it's invaluable (and much better than C# in Depth IMO). It covers just about everything in C# and is remarkably up-to-date.

Joe Albahari has had to work with just about every feature in C# (he's the author of LINQPad) and it really shows in the book.

Re: Performance Improvements in .NET 6

#30
post #25
post #9

For large enterprises, that use AWS / GCE / Azure, these improvements directly translate into huge savings in server capacity. I have always loved .NET and it keeps getting better and better. They have shown remarkable flexibility to throw away ideas that don't work and have modernized. A large part of that is due to active involvement of the community. This could be a new model moving forwards, a software worlds equ…

I’m thorn on that. As someone who has had intermittent periods of .NET, it’s a complete mess every time I’ve come back after a couple of years off and figuring out what new APIs are the new thing to use, which have been deprecated and when looking for a solution of something involving e.g. configuring stuff in the web server request handing stack it’s a real confusing mess. Docs of course aren’t all up to date and ar…

> It’s way worse than React in this regard (if not only by its sheer size and larger scope)

FWIW, I've used React for 18 months now. Except Java and classic core PHP it is one of the most stable platforms I've developed on.

So, in my view being less stable than React isn't a big problem.

Post reply on HN