4 ms·
But with software, sometimes there comes a time when it really should stop growing. When any further "enhancements" make the software worse. It's something I'v
by JohnFen 3y ago
But with software, sometimes there comes a time when it really should stop growing. When any further "enhancements" make the software worse.
It's something I've seen countless times in my life. A piece of software achieves something pretty close to perfection for its task, but the self-imposed "need" to continue development on it ruins it.
- rzzzt 3y agoDoes it read mail and/or contain a subset of Common Lisp?
- worthless-trash 3y agoAll software will eventually grow to send email. And lets be honest, if its not written in lisp, are you really trying ?
- systems_glitch 3y agoAbsolutely. Some things go into bugfix-only mode because their code has reached perfection for the 99% use case.
- broeng 3y agoAnd then we fear it's a dead project, and move on in search for something else with active contributors.
- JohnFen 3y agoCertainly not everyone. Personally, I pay little attention to that sort of thing at all. I don't care if it's a "dead" project or not -- as long as the software is meeting my needs, that's the only thing that matters. If/when it stops doing that, then I'll look for alternatives.
- systems_glitch 3y agoSame here. I run Slackware on all of my engineering and development workstations. It does what I want, nothing gets hosed when running updates, and I don't feel like my main job is sysadmin. But I keep getting told I need a "Slackware intervention" :P
- AlbertCory 3y agoHot take: Python 3. Totally unnecessary.
- Master_Odin 3y agoThe move to python 3 helped shake loose a number of text processing bugs with library I work on, that was never caught in python 2 with its loose goosy text type handling.
- JohnFen 3y agoBut as an end user, it's made using applications based on (or even tangentially using, as I learned first-hand a couple of months ago) Python highly problematic due to extreme version incompatibility. I now try my best to avoid anything that involves Python.
- janoc 3y agoSorry but that's nonsense. Python 3 has been released in 2008 - 15 years ago. And the last Python 2 version has been EOLed 1.1.2020, three years ago, after a decade of deprecation! With your argument about compatibility no programming language would ever be able to evolve or deprecate/remove some features. Look at how many things changed e.g. between recent C++, Rust or C# major releases. Python had only one major revision in 15 years in comparison! If you are using software that still requires Python 2 that's very much a problem of that application and not Python. Complain to the vendor responsible, not about Python. They had ample time to update their code. End users had no business touching Python 2 for at least a decade now. And upward compatibility between the point releases of Python is (and has been) generally pretty good.
- AlbertCory 3y agoall arguably true, but it has no bearing on whether 3 was necessary in the first place. > With your argument about compatibility no programming language would ever be able to evolve "evolve" and "change" are not ends in themselves. If it was usable as it was, then there was no need to evolve or change in an incompatible way. 15 years ago: also irrelevant. World War One was unnecessary, and that was 109 years ago. Whatever issues existed are sorted out by now, but that doesn't mean it had to happen.