I mean, that's the whole point.
The joke I made above is that Java is a corridor-shooter language, and that still fits with your description: its widespread use (though fading, because its performance is pure ass) in the corporate world is mainly for the very reason that it makes programmers rather disposable, and essentially facilitates building distributed bureaucracies over agile ideas. It's a "corridor language" because there is really only one pattern for most of your development. Perl, on the other hand, is absolutely more comparable to an old-school shooter, in that it encourages the notion of there being almost infinitely many alternative ways to approach any problem. Of course that means less maintainable code by another person following you, by definition, but that's the trade-off.
As part of the proof of that trade-off: you'd have a hard time finding hardly any major tech startups in new fields (AI, IoT, embedded systems, anything) that opt for Java today. It would be an extremely unusual choice for building new technology that needs to adapt quickly.
Now, don't get me wrong--Perl is an ingenious scripting language whose incorporation of regexes as a first-tier part of the language was earth-shattering and influenced a ton of later ideas , but I haven't used it for a decade and wouldn't for building applications. My favorite language today is Rust, if I am working on something low-level and can pick freely. Rust is definitely not permissive, by the way--having the most rigorous borrowing / pointer reference system around--but nonetheless offers smart paradigms of trait composition instead of inheritance; functional programming paradigms; and smart pattern matching... all of which lead to more intelligent and nimble solutions than the nightmare of old-school OOP inheritance with stateful instances everywhere.