The Great C++ Confession

Oh honey, the AUDACITY of these programming languages thinking they're the chosen one to dethrone C/C++! Rust (the crab), Haskell (the sloth), Go (the gopher), and Zig (the lizard) are all standing around like vultures at a funeral that hasn't happened yet, just WAITING for their moment to shine. 💅 Plot twist: C/C++ has been "dying" since before half these languages were even born, and yet here we are in 2024 with the entire world still running on it. Your operating system? C. Your game engine? C++. That fancy Rust compiler you're so proud of? Written in... wait for it... bootstrapped from C++. The drama! The irony! These new languages really said "I can fix him" about systems programming and honestly? The delusion is almost admirable. Almost.

The classic programmer's transitive property. "If I know A and B, then I know C" logic taken to its absurd conclusion. Like claiming you're fluent in Italian because you once ate at Olive Garden. Next they'll say they know machine code because they touched a computer once. The confidence of someone who thinks programming languages are just Pokémon evolutions of each other.

The eternal question that separates the juniors from the seniors. Someone innocently asks you to pass the salt, and suddenly your brain is running a full stack trace on whether they want a copy of the salt shaker or just a pointer to its memory address. Pass-by-value means they get their own little salt shaker (a copy), so whatever they do with it doesn't affect yours. Pass-by-reference means you're handing them the actual salt shaker, and if they dump it all over their food, well, you're both out of salt now. This is why programmers can't have normal dinner conversations. We're too busy worrying about memory allocation and whether we need to implement a mutex lock on the condiments.

Oh, the sweet innocence of thinking graphics programming would be fun! You start with "YAY, GRAPHICS PROGRAMMING!" full of hopes and dreams, ready to create the next masterpiece. Then reality hits: you decide to draw ONE measly triangle, and suddenly your entire screen is consumed by a CRIMSON DEMON TRIANGLE FROM HELL that grows exponentially with each passing millisecond. Welcome to graphics programming, where a single vertex coordinate typo transforms your cute little shape into an eldritch horror that devours your viewport and your sanity. That's not a triangle anymore, bestie—that's a declaration of war from your GPU. The Zelda character's descent from excitement to absolute terror is *chef's kiss* accurate. Nothing says "I've made a terrible mistake" quite like watching your simple triangle decide it wants to be the ENTIRE UNIVERSE instead.

You know what's hilarious? C/C++ devs spent decades perfecting their craft, mastering memory management, understanding the dark arts of pointer arithmetic, and building intricate build systems with Make, CMake, Autotools, and whatever other arcane configuration nightmare they could conjure up. And now? They just stare blankly at their screens like they've seen the void itself. Why defend a build system that requires a PhD to configure when you could just... not? The younger devs roll in with their cargo build and npm install and suddenly the 20-line Makefile that took you three days to write feels like overkill. The exhaustion is real. Sometimes you just accept defeat and move on.

The funeral for C/C++ has been announced prematurely for decades now. Every few years, some shiny new language comes along and declares itself the "C++ killer" while C++ just smirks from its grave and continues powering literally everything from operating systems to game engines. Meanwhile, C/C++ developers are just chilling next to their own tombstone like "Oh no... anyway" while counting the performance gains their manual memory management provides. The language might be older than most developers using it, but it refuses to die with the stubbornness of that one legacy codebase no one wants to refactor.