3 ms·

> Generally these are folks who prefer the default soldier-on-in-the-face-of-errors behavior from ... perl. Nobody in the Perl world prefers that, outside of p

> Generally these are folks who prefer the default soldier-on-in-the-face-of-errors behavior from ... perl. Nobody in the Perl world prefers that, outside of people who are complete newbies. In fact, collectively Perl has been yelling at newbies for decades that anything not containing `use strict;` and `use warnings;` is almost without fail broken code, mainly because there are a lot of very old and outdated tutorials which introduce these modules as optional and/or way too late.

wyldfire 11y ago
> Nobody in the Perl world prefers that, outside of people who are complete newbies I think these are actually old-bies. They don't opt-in to `use strict;` because they like it that way. I suppose they just have an astonishingly high pain threshold.
- Mithaldu 11y ago
  To be clear here: You can be a perl newbie even after you've been writing Perl for decades. I know this because i sometimes see code like that in companies that don't value their employee education, or heck, their employee. Period. You'll have a guy who's been writing Perl for 15 years and never got past the small 500 word tutorial he once read back then. He may be old and have the years, but he's still a newbie since he doesn't know shit. That said, i've never met these people outside of said companies and especially not on the internet and most decidedly not anywhere near any sort of perl community. They've all been strict 9-5ers for whom the coding is a burden to bear to pay the bills and nothing else. The people who're old and in the community? They're on the same Kwalitee train as everyone else.