3 ms·

I was with you for the first paragraph, but not the second one. Yes, you should use a relatively small toolset and use it well. Whether that toolset is prolog

I was with you for the first paragraph, but not the second one. Yes, you should use a relatively small toolset and use it well. Whether that toolset is prolog or JS or bash or whatever depends entirely on your needs and requirements and will vary from team to team. If bash scripting meets your needs, then use bash scripting! There's nothing wrong with it. Likewise for clojure or C# or any other tool.

rho4 7y ago
In my opinion there is everything wrong with bash scripting. As per the 1st paragraph, I would argue to use your main language instead.
- Singletoned 7y ago
  What if bash scripting is your main language?
  - rho4 7y ago
    Then use bash scripts for everything. Good luck.
  - djsumdog 7y ago
    I would update my CV. Don't get me wrong, you can do a lot of good stuff in Bash. But if I want to do a lot of more complex processing, having a language with useful iteration constructs like Python, Ruby, Groovy or others needs to be an option that's on the table.
- djsumdog 7y ago
  Most companies have sets of supported languages and you need to use the right tool for the job. For small one-off tasks or simple services, your company should have a template for writing those in a good scripting language: Python, Ruby .. something you can write tests/specs for if it grows, that has a good amount of programmers you can hire, etc. Your core service apps might be written in something different, that can scale up, whether that's a JVM lang (Java/Scala/Clojure/Kotlin) or a .NET (C#/VB.Net) or Elixir or Rust or whatever depends on a lot of things. You want to have something your core programmers enjoy writing in, but also something you can find new people for as your company expands. It can be a delicate balance. You can have multiple core languages (my current company is Node/React for most front end, React Native for apps, Clojure for almost all backend, some .NET and Python/Go/Terraform for all devops). It's best to have a core tech stack with some choice than just let every team do anything in whatever. But of course, it's dependent on your company and market. Your mileage will vary.

rho4 7y ago

In my opinion there is everything wrong with bash scripting. As per the 1st paragraph, I would argue to use your main language instead.

Singletoned 7y ago
What if bash scripting is your main language?
- rho4 7y ago
  Then use bash scripts for everything. Good luck.
- djsumdog 7y ago
  I would update my CV. Don't get me wrong, you can do a lot of good stuff in Bash. But if I want to do a lot of more complex processing, having a language with useful iteration constructs like Python, Ruby, Groovy or others needs to be an option that's on the table.
djsumdog 7y ago
Most companies have sets of supported languages and you need to use the right tool for the job. For small one-off tasks or simple services, your company should have a template for writing those in a good scripting language: Python, Ruby .. something you can write tests/specs for if it grows, that has a good amount of programmers you can hire, etc. Your core service apps might be written in something different, that can scale up, whether that's a JVM lang (Java/Scala/Clojure/Kotlin) or a .NET (C#/VB.Net) or Elixir or Rust or whatever depends on a lot of things. You want to have something your core programmers enjoy writing in, but also something you can find new people for as your company expands. It can be a delicate balance. You can have multiple core languages (my current company is Node/React for most front end, React Native for apps, Clojure for almost all backend, some .NET and Python/Go/Terraform for all devops). It's best to have a core tech stack with some choice than just let every team do anything in whatever. But of course, it's dependent on your company and market. Your mileage will vary.