mjsabby

7 ms·

1.
by mjsabby 5mo 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.
2.
by mjsabby 11mo ago
I got it at 39, still have it, you'll be fine.
3.
by mjsabby 4y 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
4.
by mjsabby 6y ago
Can you elaborate “never rely on countermeasures”. What are you referring to?
5.
by mjsabby 6y 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
6.
AutoCrane: Shipping Containers Safely on Kubernetes(timmydouglas.com)
2 points by mjsabby 6y ago|0 comments
7.
MsQuic – QUIC Implementation from Microsoft(github.com)
153 points by mjsabby 6y ago|84 comments
8.
by mjsabby 8y ago
Thanks for the suggestion, I've modified the graphic.
9.
by mjsabby 8y ago
It's in milliseconds. I'm going to update the post and add that note, but omitting values was a business decision, sorry.
10.
by mjsabby 8y 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
11.
by mjsabby 8y 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.
12.
by mjsabby 8y 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.
13.
by mjsabby 8y 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
14.
by mjsabby 10y 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&
15.
by mjsabby 11y 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.
16.
ETW2SQLite and ETW2JSON: Convert Your ETW Logs(github.com)
1 points by mjsabby 11y ago|1 comments
17.
by mjsabby 11y ago
This wiki page details what LLILC will be doing to get GC Support as required by the CoreCLR: https://github.com/dotnet/llilc/blob/master/Documentation/ll... Andy Ayers from the LLILC team will be p
18.
by mjsabby 11y ago
Have a look at the FAQ: https://github.com/dotnet/llilc/wiki/LLILC-FAQ Q: How does LLILC relate to the .NET Native work? A: .NET Native provides a broad tool-chain, targeting Windows. The LLILC AOT could be
19.
by mjsabby 11y ago
LLILC is absolutely interested in upstreaming and in fact, at least one big change (prelim COFF support for MCJIT) is already upstreamed ( http://lists.cs.uiuc.edu/pipermail/llvm-commits/Week-of-Mon-... ) in additio
20.
by mjsabby 11y ago
Having multiple code generators is not mutually exclusive, and this effort does not mean MSFT is ditching any existing AOT (or for that matter JIT) compiler projects. One of LLILC's major objective is give the community an MSIL fronten
21.
by mjsabby 11y ago
Mailing list post: http://lists.cs.uiuc.edu/pipermail/llvmdev/2015-April/084459... And also check out LLVMSharp -- http://www.llvmsharp.org which gives LLVM access to .NET Disclaimer: I'm inv
22.
LLILC – LLVM-Based Compiler for .NET CoreCLR(github.com)
220 points by mjsabby 11y ago|43 comments