> There's a natural progression from Bash to Perl to Python, each more powerful than the previous. As someone who moved in the opposite direction, I can't disa

> There's a natural progression from Bash to Perl to Python, each more powerful than the previous. As someone who moved in the opposite direction, I can't disagree more strongly. Python is great if you want to write programs, but that adds a huge overhead over time, even in a simple language. When I started using Perl, I feel like I really became a DevOps engineer. I built an automated test framework, deployment and monitoring tooling. I wrote scripts to automate processes large and small. It was the perfect scratchpad for getting an idea down with a working implementation, it was as free form or structured as I wanted it to be at any time. Over time, my familiarity with Bash started to cover a lot of the smaller Perl tasks I was used to. To automate some simple testing of a REST API, is Python / Perl _really_ needed? A simple bash script could read data from a text file, then run curl commands in parallel while logging failures. Hell, use jq and you can process the JSON responses trivially too. If Bash lacks power, I haven't ran into many situations where this was my issue.