Nor sure what this article is trying to convey?
Is it about grepping wrong defaults for bash?
Is it about mentioning the protagonist as much as often?
I've read it twice now, and I feel ignorant.
The environment variables count towards the argument limit. To a casual shell user, this is non-obvious and typical error messages are bad and don't even mention it.
They say "Argument list too long" even when the argument list (argv) isn't too long, the environment list (envp) is.
So the author went through an investigation to figure out what was happening, and decided to write down her findings.
----
On a personal note, reading this caused me to look at fish's error message in this case. It mentioned "environment list", but tbh that's still too jargony and non-obvious.
So the next version of fish will now explicitly mention "environment variables" in the error message here, and it will print a hint if the environment variables account for over half the limit.
This is a great illustration of how Bash and similar shell dialects are convenient for interactive use but terrible as a programming language.
Change my mind: Bash is the PHP of operating systems. Any Bash script becomes tech debt the moment it is written.