I can't even get developers to read error messages, let alone documentation. The number of times I've had senior (by title) individuals send me screenshots of stack traces asking for help is too damn high. This field is a joke.
Sorry you're getting downvoted and probably flagged, but I agree with you. The fact that someone made an entirely separate thing for this is mind-boggling, when a simple shell alias solves this problem, and takes literally 60 seconds to set up.
But then again, this is the same industry that thinks shipping 600 MB of Node packages and an entire instance of Chromium is what it takes to use ffmpeg, so, I'm not surprised, just disappointed.
It is ignorance, because aliases and shell scripts have existed for eons, and this is an overkill solution for a non-issue. I have a bunch of aliases for common flag combinations; I haven't released any of them as entirely separate programs.
Except there are about a million ways to do this that don't involve releasing another tool. Everyone I know (including myself) would make an alias, that's entirely what they're for. If you want to get really fancy, you could make it a function in your shell's rc file. Or if you're REALLY zesty, you could even write an entire shell script for it.
To a senior, tools like this make no sense, because they're unnecessary, and contribute to bloat and waste, both for systems, and for the time spent.