I'm glad this was posted in response to "python 3 is killing python". We've just decided to move our simulation software to Python 3 and the previous article had me a bit worried about Python's fate. So it's good to hear a robust defense of Python 3, but there's also a bit of attitude in this post that I don't like: the idea that Python 3 is just the product of a bunch of volunteers coders having fun, why should they care about you and your problems with Python 2/3? You do what you want to do (including forking Python 2 if that floats your boat); let the Python devs do whatever floats their boat.
But this attitude is actually not ok. Python is not just a fun experiment; it is a successful language as the Python.org website is eager to illustrate in the "Success Stories" section. Many businesses depend on it, a lot of money and innovation rides on it. And evidently, the python community thinks that's a good thing, it's maybe even a bit smug about it. So it's not acceptable to say that Python's devs can just hack away in a bubble of self interest. While Python 3 is hopefully not actually killing Python, ignoring the concerns of everyday Python users will kill Python. According to this author, that's ok because the Python devs are just volunteers having fun. But I don't think those devs would say that's ok. Python's success is a big part of what makes all their work relevant. So even if resistance to Python 3 is misguided, it is somewhat pervasive, and the Python community ought to have a good (i.e. not merely dismissive and patronizing) answer to those concerns.
See, you're expecting volunteers to make a powerful free language which businesses use commercially, and then when they want to change it, you expect them to do it in a way that is commercially viable and easy for those businesses?
Why don't you expect the businesses that make money using free and open source software to donate money and always make sure to steadily port their code to newer versions of python? Because it's too expensive? Because it's cheaper to let the community of volunteers do it for them for free? I think that's ridiculous.
And when their code becomes old and unmaintanable because they didn't want to spend money earlier, they complain that it's the communities fault for their problems? Why should the volunteers care? They make what they want to use, they aren't employed by the businesses. Should they hold back their ideas and their project because it's too expensive for some business?
Why should the volunteers care? They make what they want to use, they aren't employed by the businesses. Should they hold back their ideas and their project because it's too expensive for some business?
You're right. The devs have every right to just do what they want. They're not beholden to my bottom line. But my point is, if they do that, that means they're ok with Python not being useful to other people, and they're ok with Python's user base dwindling away. But if the Python community was ok with that, they wouldn't brag about Python's success. Python.org wouldn't have a gigantic "Success Stories" section. Python wouldn't bother to promote itself at all, because it's just a bunch of volunteer devs having fun. But that's not the case. You can't have it both ways. If Python's success among the broader programming community is a good thing, then you can't just say "here's a phone, call someone who cares" when that community raises concerns.
that means they're ok with Python not being useful to other people,
No, that just means they put the project and the vision of the project above what commercial business users want it to be to suit their own commercial and financial means. Python remains useful to other people, it's just that those people aren't the ones that are tied up with legacy code, and are willing to change and make better, new things. And it's not like the core devs are forbidding the use of older python versions. It's not like 2x is suddenly going to become unavailable and apps all over the world are going to crash. Older versions are available and they can be forked, and modified and hacked. It's just that they, the core devs, want to move onto other things, better things. If bussineses have a financial interest in maintaining old code then they should be willining to spend money on it and either do it themselves or pay someone to else to do it. They should be proactive about it instead of expecting the core developers and the community to do it for them.
and they're ok with Python's user base dwindling away.
I'm not disagreeing. If I were a Python dev, I would want to make a clean break from Python 2 and develop new innovations in Python 3. Backward compatibility sucks for keeping a language clean and efficient. And that's what they did, and now the core Python community is talking about all the great things Python 3 can do. But that is naturally going to put off folks who manage production code bases in Python 2. Those people, who otherwise love Python, get the shaft. It's very hard for them to justify the risk and cost of upgrading working code. So if you're going to promote Python 3, you have to be a bit sensitive to the fact that a lot of Python users are going to say "that's great, but it doesn't benefit me at all."
My take on this is that Python 3 proponents have to stop pushing Python 3 on people. And pushy is how it comes across. Everyone has to weigh the costs/benefits of moving to Python 3 for their own purposes. Some speaker at pycon, no matter how authoritative, does not have a valid say over whether I should port my code from 2 to 3. If you want people to do something, don't tell them to do it, make it as easy as possible (e.g. 2to3.py), and then let them decide if/when to do it.
My take on this is that Python 3 proponents have to stop pushing Python 3 on people.
From the article:
Not everybody can forget about Python 2 completely right now, but not everybody needs to move to Python 3 at all, or to use any particular programming language for that matter. Go do what makes you happy.
What makes me happy is using Python 3.
The only reason people seem to do this is because people attack Python 3 with so much fervour.
Move when you want. There are masses of support for people using Python 2. Nobody sane is arguing with that. We're just asking you to allow people not tied down to be able to use version 3 without having a hundred "Python 3 sucks", "Python 3 can't do bytes", "Python 3 is killing Python", "Nobody uses Python 3" posts thrown at us.
28
u/ThePurpleAlien May 28 '14
I'm glad this was posted in response to "python 3 is killing python". We've just decided to move our simulation software to Python 3 and the previous article had me a bit worried about Python's fate. So it's good to hear a robust defense of Python 3, but there's also a bit of attitude in this post that I don't like: the idea that Python 3 is just the product of a bunch of volunteers coders having fun, why should they care about you and your problems with Python 2/3? You do what you want to do (including forking Python 2 if that floats your boat); let the Python devs do whatever floats their boat.
But this attitude is actually not ok. Python is not just a fun experiment; it is a successful language as the Python.org website is eager to illustrate in the "Success Stories" section. Many businesses depend on it, a lot of money and innovation rides on it. And evidently, the python community thinks that's a good thing, it's maybe even a bit smug about it. So it's not acceptable to say that Python's devs can just hack away in a bubble of self interest. While Python 3 is hopefully not actually killing Python, ignoring the concerns of everyday Python users will kill Python. According to this author, that's ok because the Python devs are just volunteers having fun. But I don't think those devs would say that's ok. Python's success is a big part of what makes all their work relevant. So even if resistance to Python 3 is misguided, it is somewhat pervasive, and the Python community ought to have a good (i.e. not merely dismissive and patronizing) answer to those concerns.