I much prefer the option to create either an object orientated distribution, or a non-oo one.
If I don't need to keep any state, why bother with the added complexity? OO adds overhead, no matter how slight.
Among my list of familiar languages, Python is one. Python is "everything is an object". I'm a guy who prefers simplicity, and freedom to choose. If I want to create a list of functions for very basic mathematical calculations purely written in C fronted by Perl with no OO overhead, I like that choice. If I want to represent a Tesla vehicle that has thousands of always-changing parameters that requires a mechanism to maintain that state, I want that choice. When I want to wrap another language's API where I want to provide both a procedural and an OO interface, I want that choice. I feel that everything is an object is a bit overkill. That's why I didn't diverge with the then Perl6 crowd (in fairness, I did give it a very good run to be certain though).
Important part is the availability to choose. Even when I do write OO distributions (most of mine are), I don't use anything but the core perl OO functionality. No Moose or equivalents etc. Even when Corinna comes into play, I very much doubt I'll change my ways.