Announcing new Series on CLR

Chronicles of Article Announcements

Hi there!

This won’t be your typical Bitesized article, but rather an announcement for a new deep-dive series that I’m planning to be covering over the next months. And of course, I’ll be covering it along the C++ Memory Management series!

But let me give you a quick backstory first. Do you know what seems to make these Bitesized Articles interesting? It's the fact that the topics I'm covering and questions I'm answering are something that I had to learn about recently; most of the time at least. So what makes it effective is that I'm asnwering the way I'd hope somebody would have explained those things to me.

To cut the long story short, I started developing interest in understanding what .NET does under the hood. And if you search around, it doesn't take long to figure out that it's the CLR (Commong Language Runtime) that provides the, you know, actual Runtime for executing that code.

So I went along and picked up a book called CLR via C# by Jeffrey Richter (amazing author btw) and all it took was a FIRST chapter to get myself hooked AND make me want to explore more in-depth :)

What that means is that I'll be starting a new series of Bitesized Engineering articles (along with C++ ones) on the CLR and the inner-workings of it. And frankly, I think it's INCREDIBLY COOL stuff to do a deep-dive into!

Here’s a cool image to spike your interest:

If you're a .NET developer, or just a general curious person, I think this is something you'll want to follow. So if you haven’t already, now might be an interesting time to subscribe to this newsletter:

P.S. Here's a cool piece of info - all C#, F#, VB, etc. code gets compiled to Intermediate Language (IL). And that IL is then executed by CLR. That's probably old news. What's COOL is two things: 1) CLR compiles your code to native code just before it gets executed (i.e. JIT compilation) and that has some really nice "consequences" that I will be discussing, and 2) There are TONS of languages that can compile to IL and get executed by CLR (e.g. C++, Python, Ruby, PHP, Powershell, etc.). Technically speaking, as long as you adhere to Common Type System (CTS), you could compile any code to IL, and have it executed by CLR. And I just think that's absolutely cool :)