I can taste this.

Billionaire collects more government welfare.

Absolutely. I once wrote a server for a factory machine that spawned child processes to work each job item. Intentionally we did not free any memory in the child process because it serves only one request and then exits anyway. It’s much more efficient to have the OS just clean up everything and provides strong guarantees that nothing can be left behind accidentally for a system where up time was money. Any code to manage memory was pointless line noise and extra developer effort.

In fact I think in the linker we specifically replaced free with a function that does nothing.

I don’t blame you. I have to use a professionally sometimes and I am not a fan. It’s an absolute behemoth of the language filled with warts and cruft.

Sometimes it is the best choice for a project, but I prefer languages with simple, orthogonal concepts.

Pfft compilers. Just use assembler.

You call the destructor. It’s simply not automatically done for you with the concept of going out of scope.

Back when C++ was simply a text pre-processor for C, you could see these normal function calls. You can still see them in the un-optimized disassembly. There’s nothing magical about a destructor other than it being inserted automatically.

Also goes for mobile. You use more memory and apps get killed.

A middle ground is a memory pool or an object pool where you reuse the memory rather than free it. Instead, you free it all in one operation when that phase of your application is complete. I’ve seen this done for particle systems to reduce overhead.

I absolutely love the term clankers. It’s the perfect blend of dystopian cyberpunk and the very real threat of AI.

I’m the tech lead on a three-year-old project that’s entirely in C. It is my full time job to write C89.

Bingo. I thought something probably happened to your terminator.

That sounds like it could be memory corruption. That should not happen because every string should be separated by a null terminator.

Not freeing your memory at all is a memory management strategy. I think some LaTeX compilers use it as well as surprisingly many Java applications.

It being from the mod makes this even more funny.

I like this solution because I can have the need filled without a central server. I use old-fashioned offline backups for my low-churn, bulk data, and SyncThing for everything else to be eventually consistent everywhere.

If my data was big enough so as to require dedicated storage though, I’d probably go with TrueNAS.

An in-app-purchase screen would have been a great fit.

It reminds me of those bills that do the exact opposite of what they’re named.

Can I be the wife? 🥺

They pay me at least.

I main Fedora 42 KDE and NVidia. Drivers are definitely not out of the box, but I found them easy enough to install by adding a repository. Just a data point for consideration.