Bad and good doesn't depend so much on the language but the coder.

IMO there's also a component where a good coder will pick the best suited language for the task, but will also pick something that the rest of their (potentially less skilled, junior or even intern) team won't be scared away by.

If you're mostly just running a few commands and writing to a bunch of files, bash is great and does that in almost no code and remains quite readable. Like, a backup script for a database is essentially a bash one-liner. I'm sure it's also easy in a Perl script, but just seeing a .pl file can scare some admins whereas they know what to expect if they see a .sh.

Then there's also a component of, what does the company uses. If the company runs Ruby apps, then I'd write tooling in Ruby. If the company runs PHP apps, some of the tooling will be written in PHP.

It's very circumstantial in the end. I'll definitely whip up some Perl if it's advantageous, but really most of the time it's just wrapping an rsync or whatever, and at work it's usually just some glue or bootstrapping something like Puppet or Ansible. Not a fan of those personally but it's a safe bet for my role and industry.

On the personal side, I tend to turn to what's my favorite language at the moment, so lately I've been practicing my Rust.