My usual operation and maintenance tool is Bash, and Python is mainly used to do some algorithmic calculus. Because my daily maintenance task is mainly file system maintenance, the contrast language should be combined with the scene.
Most application requirements can be completed in various languages, but the degree of difficulty is different. Choosing a language depends on the proficiency of the developer and the complexity of the requirements.
If it is only a "grep" requirement, it is easiest for you to choose Bash to execute grep. Use awk if it's a little more complicated, and perl if it's more complicated. It is thankless to use a more common language.
If it is a matrix computing requirement, perl's array can kill you, and bash's pipeline can kill the machine.
My following views are bound to cause controversy (especially PHPer). I tend to divide high-level languages into three categories:
1) C/C++
It is possible to write operating system and operating hardware. It can solve all problems, but most internet projects should not be used.
2) neutral Java/Python/Ruby/. Net series.
This is the main language for doing projects, balancing development efficiency and execution efficiency. There are no obvious bright spots and no obvious shortcomings.
3) Special PHP/Bash/Perl.
In some specific fields, we should choose these languages with special skills. The demand is more and more comprehensive, the shortcomings of language are used more and more, and communication should be controlled.