Like I said, this one was transparent about what it was doing. But it sets a dangerous precedent.
reply
???
Are you aware how irrelevant this "precedent" is or are you mistaken about the meaning about the word "precedent"? People have been posting terminal commands on the internet for decades now.
That's like saying someone stealing from Walmart last week was a precedent. It's not. Theft has existed forever, it's not a "precedent"
reply
Maybe precedent is not the right term here. Maybe enabling bad behavior fits better?
I think the post was a bit ill formulated. I think the post was less about that specific command but more generally about running random code without verifying or not taking any precautions.
At least that's how I read it.
reply
Yeah that's the message I got too. The terminal command in question is harmless, and OP explicitly says this along with saying it was transparent about what it is doing, but the point is to be wary of blindly pasting terminal commands if you are unsure about exactly what they do. It takes five seconds to paste them into Google before running them on your system.
It wasn't that long ago people were posting shit like "make your Mac 10x faster by running rm -rf ~/" and "delete system32 it's a virus" and yes people actually fell for that shit.
When people get into the habit of blindly trusting terminal commands without understanding what they're doing, they can easily fuck their shit up.
The tl;dr is simply "don't trust, verify."
reply
open <path>.pdf. Like literally. One has to be a special kind of regarded to not know what their're doing. It doesn't get more simple than that