3 ms·
It seems like there's no ex-Apple weighing in. I worked there ~5+ years ago now & the OS-bundled versions were such a pain that even internally we were avoiding
by vlovich123 7y ago
It seems like there's no ex-Apple weighing in. I worked there ~5+ years ago now & the OS-bundled versions were such a pain that even internally we were avoiding them. I'm not 100% sure but IIRC the issue with having python bundled is the OS is that the specific version then became required to ship meaning we were stuck on ancient versions of Python2/Python3 internally (& same for Ruby probably) to make sure that externally people relying on specific behaviours stayed functional. Additionally having them (or at least Python) installed at the system level caused all sorts of havoc in terms of interplay with other Python versions installed via homebrew if you weren't super-careful with how your paths resolved (& sometimes even then). Finally, externally most Python shops would end up installing Python via other means (e.g. homebrew) to make sure they're using the latest version & using virtualenvs which are best-practices & what we ended doing internally for our scripts too. The title & article is pure FUD - there may be reasons to worry about whether macOS remains UNIX (I'm personally not too worried) but "they're no longer pre-installing scripting languages by default" is so far from that it's laughable.
NOTE: All of this is my own personal opinion & viewpoint and in no way should be construed to represent any secret internal knowledge of Apple's internal reasonings & whatnot (I have none)
- saagarjha 7y ago> It seems like there's no ex-Apple weighing in. I think you’ll find that they often do weigh in, but without announcing it because they’re trying to avoid providing information that would force them to put the disclaimer you did ;) > I'm not 100% sure but IIRC the issue with having python bundled is the OS is that the specific version then became required to ship meaning we were stuck on ancient versions of Python2/Python3 internally (& same for Ruby probably) to make sure that externally people relying on specific behaviours stayed functional. Additionally having them (or at least Python) installed at the system level caused all sorts of havoc in terms of interplay with other Python versions installed via homebrew if you weren't super-careful with how your paths resolved (& sometimes even then). I believe this is LLDB linking against Python 2 in a way that is pretty much incorrect. I think Python 3 got a bump recently? For once this isn’t completely Homebrew’s fault :P
- vlovich123 7y ago> I think you’ll find that they often do weigh in, but without announcing it because they’re trying to avoid providing information that would force them to put the disclaimer you did ;) That may be true in general but this specific thread appears to be filled with wild speculation without attempting to understand the motivations behind this move, hence why I felt the need to try to provide what I hope is some more meaningful context.