NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.
All the Perl that's Practical to Extract and Report
In the near future, the probability is close to zero. In the distant
future, I'll be dead, and posterity can do whatever they like... :-) --lwall
Stories, comments, journals, and other submissions on use Perl; are Copyright 1998-2006, their respective owners.
Linux not the best example (Score:2)
The regressions in Linux kernel upgrades are often a nightmare. Like the recent ACPI regressions in the current kernel. What a mess.
Re: (Score:1)
That wasn't a regression. It was a documented deprecation that happened as documented. The fact that nothing in userspace updated for it was annoying, though, I'll agree.
Fortunately, perl won't have that problem since it has a policy of not breaking old code, and people regularly test blead against the entire CPAN.
Re: (Score:2)
All I know is that the latest linux kernel broke sleep/restore for a LOT of hardware.
Re: (Score:1)
> Fortunately, perl won't have that problem
The desire not to break things slows down the release cycle.
The desire not to break things for other people is a good idea. The slowing down of the release cycle is not such a good idea.
If the porters change their mind about that, what would happen? Would smoking contain the chaos?
Pursuing the linux analogy, what corresponds with the testing distributions like Fedora and debian testing in the perl context?