3 ms·

I (25 years working with GNU/Linux) usually name my bash scripts `something.sh`. I think it's debatable wether it's always good or bad, and when specifically it

I (25 years working with GNU/Linux) usually name my bash scripts `something.sh`. I think it's debatable wether it's always good or bad, and when specifically it can be a good idea to leave out the `.sh`. Also, it doesn't look like you looked into the game and came out with some conclusions. It looks more like you superficially had a look, you had a thougt and rushed to comment here about what you believe is a deadly sin. I personally never enjoy this kind of comment, as there's not much thought behind them. I tried it (before recommending to a teammate) and I also noticed some things that could be improved. But it never crossed my mind to post a judgement on the project after trying it out for just five minutes.

Annatar 4y ago
- primitivesuave 4y ago
  It may benefit you to read the HN Guidelines: https://news.ycombinator.com/newsguidelines.html https://news.ycombinator.com/newsguidelines.html, specifically the "In Comments" section. > Be kind. Don't be snarky. Have curious conversation; don't cross-examine. Please don't fulminate. Please don't sneer, including at the rest of the community.
  - Annatar 4y ago
    It does not benefit me: you mistake niceness for kindness. There is little I can learn from you and your guideliness when you yourself cannot tell which is which.
- franknstein 4y ago
  It seems like you are teaching others how to teach. Is that your area of expertise?