It originates from the PEBKAC RTFM subculture of everything being
your fault, because
you haven't memorized how to touch-type 150 command line tools, and every possible switch to pass each of them, plus the arbitrary positioning of arguments in between.
Everyone's just supposed to know that X.org windowing environments are totally insecure, and that's why system administrators refuse to be caught dead using one, production or not, with or without their custom, backlit Cherry MX keycaps.
Do your homework, and read the entire corpus of source code, no matter whether it contains more characters than the library of congress. If you didn't build the binaries yourself, then you aren't entitled to lay blame. You caused that screen flicker by being part of the problem, and not part of the solution. If you were a guru, you'd already know what's wrong. Learn to fix your own problems.
Have you ever heard of Aesop's fables? Here's a little parable to help relate why free software is always 100% perfect as is:
https://en.wikipedia.org/wiki/The_Little_Red_Hen
Everyone's just supposed to know that X.org windowing environments are totally insecure, and that's why system administrators refuse to be caught dead using one, production or not, with or without their custom, backlit Cherry MX keycaps.
Do your homework, and read the entire corpus of source code, no matter whether it contains more characters than the library of congress. If you didn't build the binaries yourself, then you aren't entitled to lay blame. You caused that screen flicker by being part of the problem, and not part of the solution. If you were a guru, you'd already know what's wrong. Learn to fix your own problems.
Have you ever heard of Aesop's fables? Here's a little parable to help relate why free software is always 100% perfect as is:
https://en.wikipedia.org/wiki/The_Little_Red_Hen