Post #1944977

I believe in "done" software. Tools, things with a very defined purpose can be thought out, launched, adjusted and at some point, "done", meaning it has a well define scope (hopefully small), addresses and solves an issue. After this, only bug fixing. With the software being small, bug fixing should be infrequent. If someone using the software wants more, they should try the classic unix approach: compose with another small tool. Not talking about bloated corporate software