5 ms·
But that’s beyond conservative, Python3 isn’t new, it’s more than a decade old at this point. I can understand that in some industries you don’t easily upgrade
by mrweasel 6y ago
But that’s beyond conservative, Python3 isn’t new, it’s more than a decade old at this point.
I can understand that in some industries you don’t easily upgrade, because of testing and certifications. It’s however also possible to put of upgrades for so long that it becomes reckless. If you’re stuck on Python 2.7 in 2021, and your code could kill people, you’re putting people in danger by being reckless.
I’ve also seen people claiming a need for stable platform as a reason to not upgrade. Well, running Windows Server 2008 in 2021 you indeed have a “stable” platform, but it should come as no surprise when modern protocols and encryption isn’t working.
- pjmlp 6y agoYesterday in the Java thread I mentioned having done some Java 1.4 stuff in 2016. The customer was running Red-Hat Enterprise 5.0, and it was going to stay that way as long as Red-Hat would be willing to support it.
- sofixa 6y ago> The customer was running Red-Hat Enterprise 5.0, and it was going to stay that way as long as Red-Hat would be willing to support it. Making the migration when RH stop supporting it extremely complex and expensive, instead of iterating.
- at_a_remove 6y agoOddly, not killing people is the reason for the very slow iterations.
- jacquesm 6y ago> If you’re stuck on Python 2.7 in 2021, and your code could kill people, you’re putting people in danger by being reckless. It's comments like this that make me very sad for the software industry as a whole. No, he's not being reckless and he's not putting people in danger. The people who make breaking changes to languages, APIs, operating systems and libraries are the ones that put people in danger and that cause others to stop upgrading because they quite reasonably fear breaking changes that could have far reaching consequences. The price of backwards incompatibility is poorly understood.
- ddevault 6y agoBreaking changes to languages, APIs, operating systems and libraries are not putting lives at risk. All of the above have expressed their compatibility guarantees in clear terms. No one advertises Python as suitable for life-critical applications. It's the responsibility of the person who choses to use it for life-critical applications to understand its change lifecycle and put that into their evaluation. While I agree that in general we should care more about backwards compatibility, don't put the blame on the maintainers for bad choices in life-critical domains. Most domains are not life-criticial and it's entirely reasonable to make and meet a set of compatibility guarantees which applies to the domains you're working in.
- jacquesm 6y ago> No one advertises Python as suitable for life-critical applications. I think you just relegated python to the status of 'toy language'. But that's the wrong attitude. Just like everything will sooner or later connected to the internet, which is why it matters that it is secure, with 'software is eating the world' as pretty much the mantra of HN you should realize that any piece of software, no matter how trivial has the potential to affect lives and sometimes in the most direct way with the ultimate price - of someone else's life - as the consequence of our collective failure. And that's because of the very nature of software: it gets re-used all the time. One persons application is another persons library, one persons application is another persons service and so on. Leaky abstractions are bad enough, leaky broken abstractions can sooner or later turn out to be dangerous. Of course whoever deploys the software has the responsibility to check it for suitability. But in principle any language, OS or library has the potential to be applied in ways the original author did not foresee and if that potential can extend to life critical or life affecting purposes then that should come with a similar standard of care. How many machine learning systems are written in Python? How many of those make decisions every day regarding people's lives, some of those life critical? Are you seriously suggesting that all those people made the wrong decision in picking the language the application is written in? If so then you are most likely at odds about this with just about every developer out there who - rather than arguing with their manager about whether language 'x', 'y' or 'z' is suitable for the job will simply be told what language is on the menu and to do the job in that one based on availability of programmers and whatever is 'hip' at the moment. These decisions are not necessarily made in the most rational manner and whether you agree or disagree with that in principle it is the reality that we live in. And so 'toy' languages such as Python, PHP, Perl, Visual Basic, FileMaker and so on are all going to be used for mission critical stuff, whether you add a disclaimer or not. Better be aware of that before you throw your brainchild out into the world: you own it.
- cactus2093 6y agoSaying that it’s been more than a decade is not exactly fair. Yes the language was out then, but it took a while for even for basic practices like 2 and 3 compatible code bases to emerge, and for any of the most popular libraries to support 3. Even 5 years ago, maybe even 3 years ago the “is it compatible with py3 yet” page still had some non-trivial gaps. So it’s not like it has been feasible for most projects to migrate for a full decade, it’s only been a few years.