| I was a Perl lover once. And now it seems I understand the haters. Just don't use Perl. The language seems fine, productive, even sublime at first but you will encounter some horrible design features. Just read the following, http://markmail.org/message/h2spyi5za4qheuft -- Perl's data structure serialization is leaky. Thought you made an int ? Whoa ... serialized as a string. http://blogs.perl.org/users/rurban/2013/02/no-indirect-consi... -- A language feature causing a burnout ? Well fuck me ! That's just a tip of the iceberg. PHP, a fractal of bad design ? Perl, a quantum bomb, waiting to tick off. The Modern Perl movement is like saying "I'll close my eyes and crime ceases to exist." No best practices will save you from broken language features. The people who maintain Perl source code, are not a _fan_ of Modern Perl. They won't make "strict" the default or introduce signatures or better OOmodel. The people who proclaim "Modern Perl" won't fork. Even this release shows how clueless Perl maintainers are ! * They released a switch statement long long back * And now they mark it even as "experimental" because of the leaky "my $_" scope. Oh God ! I will never emotionally invest in another tool. EDIT: Neutral language. |
a) The poor formatting of your post as a stream of conciousness
b) The condemnation of a language based on a single relatively minor bug
c) The unsupported assertions and unrelated criticisms like not enabling strict by default