Morning bathrobe rant: late binding.

with each rant, he's becoming more logical and also more insane

What’s his end game?

I instantly bind everything into memory. If they ask me why things are slow, I just tell them to STFU and add more RAM.

Oh dear God... do kiddies today not know what a destructor is?

Late binding ...👄☕️🌬🌬...

I'm glad I understand you and your examples. Made my day. Thanks, Uncle Bob!

The best one so far. Powered by: Letftists Tears 😂

Sounds like Arena Allocators would have solved your problem. Modules/plugins create dependency coupling and obfuscates your code base, making it harder to read. In the modern world, inlined functions that have multiple responsibilities are actually more modular, acting like independent scripts that you could copy into another code base without finding all its dependencies. You can see all the business logic in 1 script, and you can view the entire problem in a way that allows the most optimization potential, and reduces the amount of code you need to keep in your head to understand it. You can see all the side effects, because they are inlined and direct, instead of being hidden away inside function calls. If you want to reduce coupling and create true modularity, there is nothing better than repeating yourself, inlining scripts, and procedurally just solving the problem with as few functions as possible. Then, editing a part of the program, can't break another part, it can only break itself. Clean code is closer to spaghetti gotos, with its indirection and obfuscated code base, hidden among many files, which is actually worse than gotos, which can be reasonable if they jump to nearby sections, jumping out of loops or to the beginning of loops. Gotos are generally easier to follow than clean code object oriented virtual functions. Procedural code isn't spaghetti, its just solving the problem in the most straight forward honest way possible.

Basically all the functions in all the code you write in C++ game engines are virtual