re: Don't Use Bash for Scripting (All the Time) VIEW POST

TOP OF THREAD FULL DISCUSSION
re: Hi, I've written far too many Bash scripts to understand its downsides. The link you provided doesn't really change my views, would you care to ela...
 

Ah sorry. I forgot that this is opinion here. Not the facts. Then if there are no facts then I didn't get at all what this articles is about. Title should be in this case 'in my opinion don't use old non readable bash scripts as it have limits, you cannot extend it with new functions and commands and it's just for repeating what you writing in cli'
Lies:

  • "Bash shines in small and efficient scripts which are designed mainly for one thing: repeating instructions you would otherwise type manually from top to bottom" Bash main purpose is to access results of commands and do something with it. Also there is hundreds of complex programs written in it like ex installations scripts
  • "Syntax of Bash is ugly and has a steep learning curve." Step learning curve because or, args and modules? None English learner will need to learn the syntax this way or that way and for them it is no difference.
  • "Writing good Bash scripts takes years of practice" In this case writing javascript take 100 years..
  • "There might come a day Bash has a good (nested) dependency system and friendlier syntax." How usage of command can be more friendly and better than is now?
  • "complexity grows too large to handle reasonably within the limits of Bash" Limits?

Instead of saying 'hey guys you can run javascript, php, python, go etc from cli directly' you blaming that bash is crap.

Eh.. Don't like negative post.
And if this is your blog and this should be just opinion about not using bash as its shit then sorry for saying lies.
I used to devs who using facts when saying anything about language syntax etc.

Thanks for your input. Since you're just obviously misreading intentionally I'm signing this discussion off with a notice that opinionated blog posts and research articles are two different things. Learn that.

  1. Opinionated articles should have subjective title.
  2. The content of article is strictly not opinionated as there are no words (about bash) like:

Introductory Words and Phrases:
I think
I believe
I feel
In my opinion
My favorite
The best
I strongly believe
From my point of view
It’s my belief
Based on what I know
I am convinced
Speaking for myself
I know you will have to
agree that
I am confident that

Transitions:
Opinion Clues
First/second/third
First of all
Next
After that
Additionally
Equally important
Consequently
Besides
Further/furthermore
Clearly
Obviously
In addition
For all these reasons
Finally
In conclusion

Opinion Clues:
Always/Never
Awful/Wonderful
Beautiful/Ugly
Better/Best/Worst
Delicious/Disgusting
Definitely
Enjoyable/Horrible
Favorite
For/Against
Good/Bad
Inferior/Superior
Oppose/Support
Terrible
Unfair
Worthwhile

Why I don't like this post, scenario: I will have some junior/mid devs at work who will write cli scripts in js instead of bash saying that js:

  1. is easier
  2. have no limits
  3. is more readable
  4. have modules etc.
  5. bash is hard to learn
  6. bash is only for repeating command in cli

When I will ask them from where they have this information, they will point this article/post (as this is not a discussion neither opinionated content about bash)
After that there will be a big conversation why we cannot use that, why we don't have node on server (to run this little script of them which should be written in bash), after that chat with manager to explain everything and half of my day will disappear.

This is a facts. Fact when 'so called' opinionated articles/post around internet making discussion with junior/mid devs at work hell.

Sharing knowledge of using js and other language in cli is amazing Mate.
Saying that bash is shit and saying to young devs that they should move to 'more advance/better/more readable' like js is more than evil.

Your scenario highlights a work culture where junior dev skills are fundamentally underestimated and undervalued. If you get kicks from lecturing to people, then show us a better example and write a post here why (in your opinion) Bash should be used for scripting. After all, DEV is a free platform.

code of conduct - report abuse