3 ms·
I think you're making a very similar point to the comment you're replying to --- that "dead" really means stability; no more worrying about changes that make th
by userbinator 7y ago
I think you're making a very similar point to the comment you're replying to --- that "dead" really means stability; no more worrying about changes that make things stop working.
Personally, as a developer who has been working on software for a few decades, I've gotten increasingly irritated with the growing churn of platforms today and the astonishing waste of time for everyone who has to deal with it. It's hard to hit a moving target or build on a shaky foundation, but that's what the state of software seems to be today. Instead of platforms approaching stability and spending time on the actual problems at hand, countless developer hours are wasting solving problems created by others "pulling the rug out from under them".
I guess the younger generation of developers just hasn't felt enough of that pain yet, or they're overeager to try new things without thinking of the consequences. I've always taken the conservative approach and as a result some of the software I've written has needed little if any new attention in decades. Some utilities I wrote 25 years ago (not in Python, obviously), I still use regularly. "It's not the tool, it's how you use it."
- cle 7y agoIt’s a combination of the tool and how you use it. And the environments that tools run in today are sometimes dramatically different than they were 25 years ago. As constraints and limitations change due to technological progress, economics, etc., so too does our software. I don’t see anything wrong with that. Nor do I see anything wrong with tools that adopt a tenet of not changing, both have value.
- falcolas 7y ago25 years is one thing. 1 year is another. There has to be a middle ground. 10 years doesn’t seem too bad. And Python 2.7 has shown that to be remarkably reasonable.
- CountSessine 7y agoI think you're making a very similar point to the comment you're replying to --- that "dead" really means stability; no more worrying about changes that make things stop working. But you're missing the same point that the parent commenter is missing - stability only came because Python 2 has been sitting at 2.7 for so long. And you're also missing the point that you can have the same stability by sticking to 3.6 or 3.7 or 3.8 or whatever your fancy is. If you stick with 3.7, I assure you that 3.7 will remain exactly the same and no one is going to pull your rug out from under you. Just don't upgrade. But don't ask for new features either.
- lopmotr 7y agoI think it will eventually settle down once people have tried all the ideas and the needs of programmers have stabilized. Kind of like how bolt threads were eventually standardized after decades of everyone doing their own thing. First comes the end of progress, then comes stability. We already have that with some computer things like basic Linux commands or HTML. You can always stop now if you want. Download the versions of everything you need and never change. But you'll miss out on the cool new hotness that you're wanting everyone else to miss out on if they stop changing too.
- lokedhs 7y agoI would believe you if it wasn't for the fact that most things being invented in software today are new. The industry keeps reinventing things that people did in the 60's without even doing it properly. Why doesn't any recent programming languages implement a proper condition system for example? It's not like working implementations hasn't been around for decades. This industry has a severe case of inability to learn from history so I strongly doubt we'll see things settle down in the near future.