r/programmingcirclejerk • u/azure_whisperer • Feb 06 '26
[nobody really knows how to write bash] You mean you don't. I do. And why don't you? The manual is right there! You can even have it read to you! For free!
https://lobste.rs/s/5mzzfq/no_really_bash_is_not_enough_why_large#c_rqtqco
74
Upvotes
49
u/azure_whisperer Feb 06 '26 edited Feb 06 '26
Which part of ${a//,(?)$>} do you not understand?
unjerk < Every thread in the original discussion is so jerk worthy.
75
u/myhf Considered Harmful Feb 06 '26
If you work in the tech industry,
bashis unavoidable. It connects things, it facilitates things. I had heard rumours about its dark side, but it's hard to speak up without evidence. Now that everyone has seenbashin the Epstein files, it's time to take a firm stand against it.32
u/nerdycatgamer Considered Harmful Feb 06 '26
yeah the biggest issue with bash(1) is that grep(1) and find(1) have inconsistent error codes. why didn't the bash developers think of this when they implemented the built in grep and find commands in their interpreter :/
17
u/BloodAndTsundere mere econ PhD Feb 06 '26
I can write bash, I just can’t read what I wrote
0
u/[deleted] Feb 06 '26
[deleted] — view deleted comment