Manuals (2014)
xkcd.com
xkcd.com
The sudoers file grammar will be described below in Extended Backus-Naur Form (EBNF). Don't despair if you are unfamiliar with EBNF; it is fairly simple, and the definitions below are annotated.
Quick guide to EBNF
EBNF is a concise and exact way of describing the grammar of a language. Each EBNF definition is made up of production rules. E.g.,
symbol ::= definition | alternate1 | alternate2 ...Programs that can get away at all with not having a manual aren't going to be the most complicated ones.
Kinda like how algorithms with O(N³) complexity have a reputation for being the most likely to screw you in production. It's not because O(N³) is worse than O(exp N), it's because O(exp N) will be noticed in testing whereas O(N³) is likely to have okay performance in testing and blow up with real-life inputs.
So in addition to not helping you understand, it will waste your time. Which can make it worse then having none.
anywhere, really, but especially here
of course many tools are unnecessarily difficult, often because the person who designed them wasn't insightful enough to simplify them, or because they're badly explained. and that does create problems, sometimes more problems than the tool solves. but many other problems are difficult to solve by their nature, and there are limits to how much tools can simplify them
there is no royal road to geometry, and blaming geometers for that fact doesn't change it
And I think you’re interpreting “tools” rather more widely than intended by the strip.