News for hackers. Stuff that matters.

A comment on The legacy of NeXT lives on in OS X (2012). Parent comment

Re:The legacy of NeXT lives on in OS X (2012) by lucasoshiro on Sunday December 22, 2024 @11:26AM (#42487314)
You can still use pip inside pyenv or similar. Pacman would install the system-wide stuff, so you won't need to bother about the libraries that a package that you have installed is using.

Mentioning this classic XKCD: https://xkcd.com/1987/. This only made sense after using a Mac. While using Manjaro it was quite organized: only the pacman-installed libraries and the ones of my user projects. Now in Mac I have the default Python, the several Python versions installed from several dependencies in Homebrew, and so on.

[ Parent | on HN ]
Re:The legacy of NeXT lives on in OS X (2012) by PittleyDunkin on Sunday December 22, 2024 @02:57PM (#42488638)
> You can still use pip inside pyenv or similar.

That seems to be the worst of all possible worlds.

[ Parent | on HN ]
Re:The legacy of NeXT lives on in OS X (2012) by lucasoshiro on Sunday December 22, 2024 @03:29PM (#42488833)
Perhaps not the best, which could be maybe something like Nix. But this is the opposite of what we have that in Mac
[ Parent | on HN ]
Re:The legacy of NeXT lives on in OS X (2012) by PittleyDunkin on Monday December 23, 2024 @10:40AM (#42495156)
I think my point was:

> Pacman would install the system-wide stuff

Most system-wide stuff is userspace. I was more referring to a divide between the OS-core (kernel, drivers, init scripts) and userspace. Upgrading userspace should not incidentally not allow the system to boot.

[ Parent | on HN ]