This weekend I went through the Landmark Forum and had to confront a big secret that I’ve been keeping hidden for virtually my entire life: the true aim of my ambitions.

Ever since I was a middle schooler, I’ve wanted to help build the first human colony on Mars....

Read More

One of the things I’ve been working on for both Helios and Akka.NET is a custom ThreadPool implementation that allows us to isolate mission-critical code from the noise of the CLR ThreadPool.

My second pass at implementing...

Read More

Time for a brief commercial interruption…

Recently Petabridge announced its professional services offerings around Akka.NET.

I’ve been...

Read More

One of the pitfalls of doing development in C#, Java, C++, or really any predominantly Object Oriented language (OOP) is how “equality” is defined.

In C#, for instance, you have the following methods that are built into every object:

• object.Equals
• the == operator
• ReferenceEquals, for explicitly checking reference equality

My personal opinion: in any managed language, checking for referential equality is a pretty bad default - and if you’re working with immutable objects then equality by reference doesn’t really work.

In C/C++, where pointer arithmetic and knowing the precise location of something in memory matters it’s a different story. Equality by reference is the correct default in that case.

What’s the right thing to do?

Read More

I originally posted this at Beyond HTTP, Petabridge’s official blog. Read More