I still use one-liners all the time, and when I need to implement a non-trivial, but small stream transformation, the resulting perl is << 1/10th the size of the unmaintainable python my coworkers would write.
Though I understand what you are saying, I sometimes feel the same with combinations of awk, sed, and other utils.
Though I suspect perl could be more powerful for that kind of processing.
I also like using perl for non-trivial stuff. For instance: parse a file, stick stuff in a hashtable or two, then iterate over the keys in sorted order, check a bunch of invariants, and then emit some other wonky format by chasing keys in the hashtables.
Some day, I hope to master the techniques in this book:
https://en.wikipedia.org/wiki/The_AWK_Programming_Language
which includes an RDBMS and assembler + interpreter, and then culminates in a 4 page section that implements make.
At that point, I might be able to switch away from perl.
All that happened is Perl 6 became Raku because some people didn't want Perl changing that much.
So Perl will jump version 6 and naturally evolve into Perl 7 at some point.
There's a perl 5.
There's no perl 6 because it's too much not like perl.
There's a perl 7 but it looks like it'll have two totally different syntaxes for stuff
And maybe there's a perl 8 but maybe with the same syntax as one of the flavors of 7?
I still see no compelling reason to get interested in perl. I have python for some stuff and go for some other stuff. What does perl do for me that these two can't?