Why Bash Sucks
Why Bash Sucks
Bash sucks donkey ass. Bash is 40 years old baggage. ( bash is born in 1989, but it's basically an enhanced Bourne Shell. Bourne Shell is born in 1979.)
- Syntax soup. E.g. For printing version, you have these variations:
--version. Sometimes options can be combined, sometimes not. Some option takes a argument, with many different syntax, some arg separated by space, some require equal sign. Order of options may or may not matter. Many options effect other options in complex way. [see Unix Pipe as Functional Language]
- Semantic noodle. E.g. Some command has recursive option
-r, others requires calling
- Randomish and cryptic command names. Part of which are juvenile humor.
- Cryptic and counter-intuitive error code. Success signal is 0. Error is a octal number. Often, you are forced to check the exit code.
- Some command are part of the shell as function, some are independent tools. E.g.
ps. Try to find if they are part of bash. And if so, is bash calling it or the independent command. [see Linux by Command Line]
- Terrible docs. Man page. Techno babble, cryptic, incomprehensible. No examples of common usage. [see Which Programing Language Has Best Documentation?]
- 40 years of baggage. E.g.
tar xvf(no dash),
- Sea of islands. Each command or tool is written on its own. No coherence.
perl. [see Perl by Example]
Programing Language Design
- Ontology of Programing Languages
- A Class of Programing Languages: Math Languages
- Why I Hate Exceptions
- Iterator, Enumerator, Abstraction Went Wrong
- Should Array Index Start at 0 or 1?
- Syntactic Semantic Difference of Map
- Should Map f Specify Order?
- Function Dependency
- Why I Hate C
- Why I Love Golang
- Why I Love Powershell
- PowerShell Complexity
- Why Bash Sucks
- Which Programing Language is Easier to Learn
- The Complexity of Java Access Specifiers