undefined | Better HN

0 pointsSpivak3y ago0 comments

> Only use that for bashisms where there's no POSIX alternative

This seems like really bad advice because the number of people writing bash massively massively outnumbers the people writing sh. Regex matching, glob matching, proper parsing, &&/||, no need to quote.

I would say the opposite, enjoy all the bashisms like (( )) [[ ]], numeric for loops, extended globs, brace expansion, ranges, OH GOD YES VARIABLE REFERENCES, and only rewrite when you absolutely have to make it work on sh.

0 comments

0xbadcafebee3y ago

Almost nobody knows all those bashisms. Nobody on the team will be able to understand it, edit it. Avoid being fancy if there's an uglier, simpler thing.

j / k navigate · click thread line to collapse

0 pointsSpivak3y ago0 comments

> Only use that for bashisms where there's no POSIX alternative

0 comments

0xbadcafebee3y ago

Almost nobody knows all those bashisms. Nobody on the team will be able to understand it, edit it. Avoid being fancy if there's an uglier, simpler thing.

j / k navigate · click thread line to collapse