In the few next posts I’d like to share with you some of the most interesting C# 8.0 features. Today we’re going to start with examining nullable reference types. Let’s see then 🙂
On the 5th of November 2018 I had a pleasure to attend Dotnetos Conference in Warsaw. It was a first conference oriented towards a single topic – .NET performance – I took part in.
I didn’t know what to expect from this event, as it was much smaller than other conferences I used to attend and actually organized by 3 .NET geeks (more about them later 🙂 ).
In today’s post I’d like to share with you my feelings about the event. I’d also like to smuggle some topics that were covered during the sessions, so you can stay up-to-date with .NET performance world’s trends and dig into them yourself.
Hey guys, I hope you’re doing well 🙂
Today I’d like to announce you a change that will happen on my blog in the days to come, so you’re not surprised post factum 😉
Knowing the idea and main benefits of JIT compilation from the previous post, we’ll now see how it fits into .NET applications execution model.
By execution model I mean a process of having a .NET Framework application actually executed on the machine (CPU), starting from having its source code written. It contains all steps and actions necessary to happen in order to transform source code (like C#) into machine (assembly) code and execute it.
Today, putting technical stuff a bit away for a while, I’d like to share with you some personal experience about Low-Information Diet. This topic concerns productivity and lifestyle, it can be said, so don’t expect any technical stuff here 🙂
So far within the .NET Internals series we focused on Small Object Heap (SOH). We know, for instance, that the LOH is not compacted (by default) during garbage collection. So how is it actually handled by the GC?
Today we’re going to see how unmanaged resources are handled by .NET, what are finalization and fReachable queues and what’s the garbage collector’s role in it. We’ll also get to know what is a dispose pattern and see how to implement it.
Continuing .NET Internals series on the blog, today we’re going to see what is generational garbage collection. You’ll also get to know what is a card table data structure and for what it’s used 🙂