Skip to main content
Unix & Linux

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

5
  • 4
    I upvoted this question and answered it, but the more I think about it only the last 2 questions fit with the site. The others a "primarily opinion based". Commented Mar 14, 2014 at 6:12
  • 1
    There is also a meta aspect in this question: While it may not help the initial answering of the question, comments like "this is not portable" can be very helpful for other readers stumbling accross the question/answer months or years later. Commented Mar 14, 2014 at 10:02
  • 2
    @Bananguin Comments saying "this is not portable" don't bother me. That's just an FYI. I've made those types of comments myself. It's the "You shouldn't use..." that bothers me. It implies that there is something wrong with the answer. That would be valid if the answer was recommending deprecated code, for example. So it had me wondering what is wrong with Bash. Commented Mar 14, 2014 at 10:52
  • 2
    +1. Especially when the question has bash tag alone, someone comments "It's bashism and not portable". When I answer a question that's tagged C, I don't care whether it's portable to Java or not. Commented Jul 23, 2014 at 14:43
  • 4
    I feel it's always good to point about that it's a bash specific feature, and not portable, just as I would point out that a GNU specific extension is being used for some utility (even though the question was tagged as Linux). I've never seen anyone say "this is a bashism and you should never use it". Commented Jan 16, 2015 at 17:57