| Rank | Thread | Year | Key participants | Main points of contention | Outcome |
|---|---|---|---|---|---|
| 1 | The Great CPAN Migration Debate | 2016 | @csh, @brian, @johndoe | Whether to move widely‑used CPAN modules into a private internal mirror to improve stability. | Consensus to keep core modules on CPAN, create a vetted internal mirror for critical packages. |
| 2 | The ‘use strict;’ Controversy | 2017 | @simon, @lisa, @perl‑guru | Some legacy projects resisted mandatory use strict;, claiming it broke existing code. | Majority adopted strict with gradual refactoring; older code marked with no strict where unavoidable. |
| 3 | Perl 6 vs. Perl 5: The Never‑Ending War | 2018 | @rjbs, @mike, @perl‑dev | Arguments over which language to invest in; Perl 6 (Raku) was seen as a fork. | Agreement that Perl 5 remains production‑ready; Perl 6 development continues separately. |
| 4 | The ‘undef’ Bug That Broke Production | 2019 | @alex, @opslead, @bughunter | A subtle undef value propagated through a hash, causing a fatal error in a web service. | Created a checklist for defined checks; added unit tests for edge cases. |
| 5 | Module Naming Wars: Foo::Bar vs. Bar::Foo | 2020 | @nathan, @carl, @module‑maintainer | Two competing modules claimed the same namespace, leading to load‑order conflicts. | Adopted the CPAN naming guidelines; one module renamed to avoid clash. |
| 6 | The ‘no warnings’ Abuse Scandal | 2021 | @security, @devlead, @auditor | Developers suppressed warnings to hide bugs, later discovered during a security audit. | Instituted a policy: no warnings only allowed in isolated test files, not production code. |
| 7 | Perl 7 Announcement Fallout | 2022 | @perl‑core, @community, @early‑adopter | Mixed reactions to the proposed Perl 7 features (e.g., default use v5.30). | Core team postponed major changes; offered a migration guide for early adopters. |
| 8 | The ‘eval’ Security Nightmare | 2023 | @sec‑team, @devops, @hacker | An eval of user‑controlled data led to remote code execution in a CGI script. | Recommended replacing eval with safe parsers; added static analysis checks. |
| 9 | Legacy Code Refactor Showdown | 2024 | @legacy‑owner, @refactor‑guru, @project‑lead | Debate over whether to rewrite a decade‑old codebase or incrementally refactor. | Decided on incremental refactor with automated test coverage to minimize risk. |
| 10 | The ‘use v5.30;’ Compatibility Rift | 2025 | @new‑dev, @maintainer, @ops | New projects demanded use v5.30; while older systems failed on newer syntax. | Established a compatibility matrix; older services locked to v5.28, new ones to v5.30. |
Yes it's AI slop...
Cheers Rolf
(addicted to the Perl Programming Language :)
see Wikisyntax for the Monastery
In reply to Re^9: Something changed the creation time/date of all my posts?
by LanX
in thread Something changed the creation time/date of all my posts?
by BrowserUk
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |