Front page | perl.perl5.porters |
Postings from June 2013
On 27 June 2013 20:59, Konovalov, Vadim (Vadim)** CTR ** <vadim.konovalov@alcatel-lucent.com> wrote: >> From: demerphq >> For me simply wanting to >> clean up the documentation for here docs would be sufficient >> justification to remove the deprecated feature. Indeed, simply wanting >> to whittle down the list of deprecated features would be. > > in reality - documentation will be opposite to be cleaned up: there will be > "starting from version x.y.z this is now differently", how thoroughly currently is. I can see what you mean, but it is besides the point for me. The point for me is that "technical reason" is poorly defined, such that one can consider "simplify documentation" as technical, or not, as suits ones preferences and biases. Which for me utterly undermines its use in determining whether a deprecated feature should actually be removed. I persist in the belief that any argument about whether a feature should be removed or not should be determined *prior* to deprecation. Deprecation means "this will be removed", not "maybe at some point in the future we will find a reason to remove this so we are marking it as deprecated now so that once we have the argument about whether there is a good reason for removing it or not we can". The latter to me is not a framework for getting stuff done. Its like veto politics, a perfect way to make it impossible to get anything done. YvesThread Previous | Thread Next