Technically speaking, I can write robust code that performs well, without the abuse of a type-checker, or the utopianism of a language ideology (ie. FP or OOP). Is it procedural, is it object-oriented, is it functional, no. It's Perl. It can be whatever you, or your team want it to be, and that's pretty cool. I usually use a mixture of all - paradigms within a Perl codebase, based on the problem at hand. Perl has a unique motto, easy things should be easy, and hard things should be possible. + paradigms within a Perl codebase, based on the problem at hand. Perl has a unique motto, easy things should feel be easy, and hard things should feel be possible. I like to think a lot about how I feel when I write code, when I write Java I feel sort of bored, and problems are almost just rocks to jump over, when I write Perl I feel as if the roof is removed from the house, and I have freedom to approach the problem however I'd like. Finally, when I have to upgrade a Perl project, no matter its age I can rest assured that it will work, and continue to work. Some people call this stagnation, I like to think of it as standardization, there will be no Perl version