The Critic is just a tool and even the most blunt force tool requires skill to use properly.
The problem is quite simple. Anyone who has the skills required to use Critic properly; doesn't need it. (That's not to say that it couldn't save them some time.)
But in the absence of those skills; it becomes the defacto expert; both reference and arbiter.
Whilst the ability to misuse it is not the responsibility of the authors; the default configuration is.
By their choice of that default configuration they've produced a gun with a hair trigger and no safety; a car with 500bhp and drum brakes; a plane that can pull 9G that breaks up at 7G.
Unfortunately, those extreme circumstances are simply: a lack of perl expertise. And that gets more common by the day. In part, because of the existence of tools like the critic.
Why pay to employ someone from the ever diminishing pool of Perl expertise; when you can download the critic and machine-apply rote as a substitute to get the tick in the "code review" check box.
Job done. Job gone.
In reply to Re^5: perlcritic compliant way to eval?
by BrowserUk
in thread perlcritic compliant way to eval?
by KeighleHawk
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |