mjsabby
Joined 12 years ago
Karma
297
Submissions
22
Member since
Oct 13
Recent submissions
Comment · 6 months ago
I've joined the B70 bandwagon as well, and have started profiling, will keep this thread updated. I suspect if we get enough of us to get even 80% of theoretical perf we'll be in a good spot. I also have two B70s.
Comment · 1 year ago
I got it at 39, still have it, you'll be fine.
Comment · 4 years ago
Lots of clinics in Vancouver BC fully body MRI scans that are not super expensive. I really do think we should just make MRIs cheap and then get the whole world to do them.
I understand the cost, time, etc. but I still think if we can stop doing other useless stuff as humanity and do this it would be net positive.
Comment · 6 years ago
Can you elaborate “never rely on countermeasures”. What are you referring to?
Comment · 6 years ago
My team did this when we moved Bing.com over to .NET Core, but it's internal. I will see if we can make it public. The problem is there are some skeletons in the closest that are irrelevant now (some since NS2.0, more since netcoreapp3.1), so I wonder how informative it will be.
Comment · 8 years ago
Thanks for the suggestion, I've modified the graphic.
Comment · 8 years ago
It's in milliseconds. I'm going to update the post and add that note, but omitting values was a business decision, sorry.
Comment · 8 years ago
Barring any bugs, the hope is that the code generated on Windows and Linux for the same architecture will be very similar, modulo calling conventions and ABI.
Then you come down to issues like Linux networking vs. Windows networking, Disk I/O differences which are interesting but from a .NET perspective less so in my opinion.
Comment · 8 years ago
Bing is huge both in codesize and technologies used, but most of it is a flavor of Windows Server 2016 (soon 2019) + http.sys + C# + Razor + TypeScript for Frontend. C#/C++ for middle and lower tiers.
Comment · 8 years ago
Windows Server 2016. All the improvements in the post that helped us are the same on Linux. I will agree though there's more dogfooding to be done. It's happening slowly but surely.
Comment · 8 years ago
Current: Windows Server 2016 + http.sys + homegrown managed layer replacement for System.Web.
Near future: Windows Server 2019 + http.sys + ASP.NET Core
Medium future: Windows Server 2019 + Kestrel + ASP.NET Core
Comment · 10 years ago
Folks, adding mscorlib binary compatibility is not going to boil the ocean or alter the "Core"-ness of .NET Core.
I implore you to take a look at this pull request:
https://github.com/dotnet/coreclr/pull/4874
All this does is changes the "core" library for CoreCLR to be renamed from "mscorlib" to "System.Private.Corelib" -- this has an important function, now the .NET team can add more backward compat features (missing types and methods) to mscorlib for those who want to use it.
If your library or product doesn't want to use it, you don't need to.
.NET Core doesn't become more bloated, it says beautiful and Core.
Comment · 11 years ago
ETW2JSON: https://github.com/ETWTools/ETW2JSON
ETW2SQLite: https://github.com/ETWTools/ETW2SQLite
The motivation for these tools is to make Windows system instrumentation data more accessible.