5 ms·

Performance Improvements in .NET 8

85 points by soheilpro 3y ago

hardware2win 3y ago
My favourite annual post from .net world and as usual - long as hell
- bencyoung 3y ago
  Yep mine too! It's pretty cool that they put this level of detail out there
- ryouko 3y ago
  > as usual - long as hell It's my annual stress test for mobile browsers lol. My chrome just crashed when I opened it on mobile, though these articles are best read with a PC + some good snacks.
  - oaiey 3y ago
    I recommend you a new phone :)
    - ryouko 3y ago
      Definitely will be looking for an affordable one with better specs haha. Had this phone for years now as I don't really need that much functionality (just mail, sms, line) as I don't spend too much time on my phone.
uticus 3y ago
Years ago I started with a .NET shop as a junior dev not because of the language or tooling, but because the job and company were a good fit. Since then I've done other languages for personal projects, but have made a career out of .NET development. There are things I don't like about the language, sure, but the backing of MS, the very large user base, and the ability to use on non-Windows systems have outweighed everything. So I'm not the biggest fan by any means, but I do recommend as a prudent decision over most other options from a business point of view.
- EMM_386 3y ago
  For my first software engineering job, I was hired to replace a Microsoft Access system that had grown too big. I decided to just write it in .Net with SQL Server, since that's what Microsoft was saying to do at the time. That was 22 years ago, when it was in beta. I've also made a career out of it. I got to greenfield another project recently, and I went with C# for the APIs.
neonsunset 3y ago
Been waiting for this for a long time! Also, insane, more than a PR a day every day on average...supposedly more than 3.5 commits a day for the whole year, each improving performance. Did not realize there were this many contributions.
ryouko 3y ago
Interesting that they've started initial work on WASM JIT. Definitely can see it a possible way for JIT languages to target the browser and still be performant. Size-wise I wonder if it'll be smaller than a fully AOT solution. We just migrated a large .net framework app to .net 6 and the perf improvements were large. Can't wait to see how much improvements we'll get from .net 6 to .net 8 as it's an LTS release so we have the go signal from management to upgrade to it.
plusmax1 3y ago
Amazing post. The thoroughness and level of detail is incredible. The length of the article is absolutely massive, trying to print it would be 218 pages. (my printer). Really looking forward to the full release.
Rapzid 3y ago
Who had to stop and go play "Let It Go"?! LOL.
zshrc 3y ago
[flagged]
- isanjay 3y ago
  Just an absurdly long article.
fomine3 3y ago
too long; but read

85 points by soheilpro 3y ago

hardware2win 3y ago

My favourite annual post from .net world and as usual - long as hell

bencyoung 3y ago
Yep mine too! It's pretty cool that they put this level of detail out there
ryouko 3y ago
> as usual - long as hell It's my annual stress test for mobile browsers lol. My chrome just crashed when I opened it on mobile, though these articles are best read with a PC + some good snacks.
- oaiey 3y ago
  I recommend you a new phone :)
  - ryouko 3y ago
    Definitely will be looking for an affordable one with better specs haha. Had this phone for years now as I don't really need that much functionality (just mail, sms, line) as I don't spend too much time on my phone.

uticus 3y ago

Years ago I started with a .NET shop as a junior dev not because of the language or tooling, but because the job and company were a good fit. Since then I've done other languages for personal projects, but have made a career out of .NET development. There are things I don't like about the language, sure, but the backing of MS, the very large user base, and the ability to use on non-Windows systems have outweighed everything. So I'm not the biggest fan by any means, but I do recommend as a prudent decision over most other options from a business point of view.

EMM_386 3y ago
For my first software engineering job, I was hired to replace a Microsoft Access system that had grown too big. I decided to just write it in .Net with SQL Server, since that's what Microsoft was saying to do at the time. That was 22 years ago, when it was in beta. I've also made a career out of it. I got to greenfield another project recently, and I went with C# for the APIs.

neonsunset 3y ago

Been waiting for this for a long time! Also, insane, more than a PR a day every day on average...supposedly more than 3.5 commits a day for the whole year, each improving performance. Did not realize there were this many contributions.

ryouko 3y ago

Interesting that they've started initial work on WASM JIT. Definitely can see it a possible way for JIT languages to target the browser and still be performant. Size-wise I wonder if it'll be smaller than a fully AOT solution. We just migrated a large .net framework app to .net 6 and the perf improvements were large. Can't wait to see how much improvements we'll get from .net 6 to .net 8 as it's an LTS release so we have the go signal from management to upgrade to it.

plusmax1 3y ago

Amazing post. The thoroughness and level of detail is incredible. The length of the article is absolutely massive, trying to print it would be 218 pages. (my printer). Really looking forward to the full release.

Rapzid 3y ago

Who had to stop and go play "Let It Go"?! LOL.

zshrc 3y ago

[flagged]

isanjay 3y ago
Just an absurdly long article.

fomine3 3y ago

too long; but read