On leaks

Ok, who’s bright idea was it to create the delete[] operator. I know that deep down, you may possibly, perhaps, in a million damned years, want a separate destructor for array as opposed to individual items, but bear in mind this isn’t the damned slab allocator you’re dealing with once that happens.
Oh, you say, but it knows that because this is an array of objects it will invoke the destructor for each object. So what, I have 4 bytes here that says you should not make me be concerned for that.
Once we’ve passed from the bounds of single-threaded, linear applications, it becomes difficult to maintain such fineries as reference counts and guarantees that we actually are damned certain that we’re the last owner of an object.
Hey, C++, I’m looking at you passing references around like chocolate. Yes; I’m damned aware of all the ways that allow you to keep the reference alive – smart references and all that.
COM – i(f*king)unknown. Oh yeah, that works all right. And if you believe that, here’s a memory manager I’ve got to sell you.
Messages. That’s pretty much it. Everything goes through the message (including the object). That keeps things simple. If you need to pass something back it has the object as well.
Incidentally, this rant was brought to you by the letters A, K and Z and the number 14. After all, it’s not prime.