Embed Notice

@bsdphk @philpem That's like Signal's kill switch which I strongly disagree with.

Software should be patched because someone found a bug, not to create change for change's sake. This sort of thing encourages a constant flood of unnecessary updates where they have to reset the kill switch and then add more stuff too.

All software should aspire to the level of stability of e.g. GNU coreutils, where the "stat" command has received eight commits in the past year including two that only changed comments and several that were code refectorings that renamed things to be more internally consistent without any binary modifications.

It should be possible for a piece of code to be *finished*. Last planned release has happened, it's feature complete and in active use, bugs will be fixed if found, but otherwise there's no reason to change it.