Hi clowns

this is fucking gold.

Every package manager sucks in a different way.

NPM gave the Node people immense flexibility so they bent it into a pretzel.

Python gave its users C extensions, so they extended it so much that it tends to interfere with the system package manager and now has a config option to disable completely for root.

C++ gave its users no packaging solution and they made megaframeworks, a rich stl, as many different kinds of wheels as there are C++ peojects, and an art of estimating whether it's worth it to implement certain basic features in their copy of well-known datastructures.

Linux distros gave the C people package managers and they made an ideological war out of it instead of working on interop.

It's actually not that bad:

1. First, you don't need virtualenv with anaconda as it comes with its own package manager "conda".

2. Second, use miniconda instead of anaconda to create barebones virtual environments without any data-science stuff pre-installed. This solves the size problem.

@ViRaS I don't use anaconda. I just use virtualenv.

@lorentz imagine my surprise when I found out cmake is essentially a dsl for building C++ projects. I thought it was just putting a bunch of shit you wanted into a file and watching it wield itself into existence, lol NOPE

@ViRaS packages are still stored on a folder structure though, very similar to that of node_modules, the only difference being that without the data science stuff the size is lesser. I get what you mean but shit is still pretty similar

i still just use pip --user, i only fuck with venv at most if i need to have older versions of package when something's only compatible with, say, python 3.8 maximum, 3.7 preferred, like stable diffusion or rvc. everything else usually stays compatible, or i just don't use a library at all and roll the one function I need myself, and Python 2.4+ compatibility happens naturally.

@AleCx04 "they both use folders, this really is the dark souls of node_modules"