3 ms·
If we go to that road, how often you need Python 2 for fileserver or build server? Now, what is the percentage of that among all MacBooks on latest MacOS out t
by nicce 5y ago
If we go to that road, how often you need Python 2 for fileserver or build server?
Now, what is the percentage of that among all MacBooks on latest MacOS out there.
- reaperducer 5y agoIf we go to that road, how often you need Python 2 for fileserver or build server? Monthly, for me. Or more often if, like last week, a new customer required it.
- Wowfunhappy 5y agoI think this mindset is dangerous. There's a really long tail of niche things people do on their computers, such that I suspect a majority of users have at least one niche need. Especially today, when Chromebooks and iPads are available for anyone who only needs basic web browsing. If you stop paying attention to the niches, they add up to a lot of people.
- nicce 5y agoYou are right, but I would say that this is quite extreme case. This is a programming language which support ended 2 years ago. Only reason to use it is to avoid turning old code base to new one. There are some serious questions if that is really a good approach. And if it is, why you need to use pre-installed Python 2 instead of installing it by yourself?
- Wowfunhappy 5y agoI expect that there are users, who are not themselves developers, who are using either apps or scripts which rely on the system-installed Python 2. They likely aren't aware that they're using Python, and they may not even know what Python is. It could be one line in one shell script block in one automator action that a coworker put together five years ago. It's okay for that stuff to break. (I wish Apple would put more effort than they do into making it break less often, but that's neither here nor there.) But, it should break in a major release, when the user is prepared for things to break. It should not break in an update that was installed automatically overnight.