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.
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.
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.
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.
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.
14 comments
[ 4.3 ms ] story [ 109 ms ] threadIt'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.
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.
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.
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.
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.
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.