or subscribe with
Join 19,300+ readers for one email each week.
Digests » 214
If you like the digest and would like to support it, please subscribe to the premium version.
Velocity helps engineers and developers build the systems that power modern businesses. Join your peers in New York City, Sep 30-Oct 3, and learn the strategies and tools you need to make your systems fast, resilient, and secure. Topics include systems performance, containers, monitoring and observability, cloud infrastructure, security, and more. Check out the program and get your pass today.
this week's favorite
How often have you gone to a GitHub repo and found that the sample code is not up to date with the latest SDK, or doesn't even build?
Ternary operator returning true/false prevents redundant assembly code generation. So adding ? true: false might lead to more keystrokes, longer code, but will have a better assembly code.
Reducing memory consumption and time taken by 80%.
About two years ago I blogged about an upcoming experimental IO API in the .NET world - at the time provisionally called "Channels"; at the end of May 2018, this finally shipped - under the name System.IO.Pipelines. I am hugely interested in the API, and over the last few weeks I'm been consumed with converting StackExchange.Redis to use "pipelines", as part of our 2.0 library update.
I’ve been digging into .NET Internals for a while now, but never really looked closely at how the ‘Just-in-Time’ (JIT) compiler works. In my mind, the interaction between the .NET Runtime and the JIT has always looked like this.