"Hey, I've noticed that when I run this script, I get an error message. It says it has failed to do step x"

A: "Have you tried running it with sudo"

"Yeah, that works"

B: "NO WAY YOU SHOULD NEVER USE SUDO THAT'S A MAJOR SECURITY RISK, ARE YOU RETARDED RUNNING THINGS WITH SUDO IS EVIL"

"Do you have an alternative solution?"

*trjirp trjirp* 🦗🦗🦗

I mean I get it.

There are risks. Sometimes you break things. Sometimes it can do really evil things.

But these days, pretty much every single hello world runs in an isolated container. If your buggy-but-super-useful script needs root for some reason, it can have it. Have fun sudo-ing all around that bare Alpine docker image.

I'm also just fed up with angry nerds yelling at me that I'm doing shit wrong, without offering any constructive feedback.

Yeah go fucking jerk yourself off with your rules, conventions and your 2000 page manuals on software design, just don't bother me with it until you have something to say which is at least functional, and preferably also practical.

Maaaaybe

Read the damn script?

@IntrusionCM Thousands of lines of obfuscated stuff in bash, perl and dockerfiles. No thanks 😅

@bittersweet

Then the "let's stuff this up the turkeys arsehole ..." Eh run it in an isolated environment to see what it does sounds like a very good idea.

@bittersweet well, you can't exactly trust that a script like that doesn't do something unfavourable if you give it sudo.