2 ms·
> Is the author not a Python developer? Well, he's a researcher. I think this is why the situation is bad in Python: we have too many non-programmers in the co
by m45t3r 8y ago
> Is the author not a Python developer? Well, he's a researcher.
I think this is why the situation is bad in Python: we have too many non-programmers in the community, that simply want something to work and get on with theirs life. If they can get by it by installing a bunch of libraries by running some command incantations as root, they're happy enough.
You don't have this problem with Node because the only niche that Node really matters is Web, and WEB DEVELOPERS know that their environment should be reproducible.
*: Even in Node this isn't really true, since we have yarn vs npm. Ruby is way more stable thanks to bundler.
- StavrosK 8y ago> we have too many non-programmers in the community, that simply want something to work and get on with theirs life The impact of those people in the ecosystem is zero, though. They don't inconvenience anyone by producing badly-written libraries, they literally do their job, produce what they want to produce and everyone is happy. I'm not sure why they get lumped in with "this problem". I don't know why I hear this a lot, it certainly doesn't echo my experience. I've rarely had dependency problems, even the regular requirements.txt (without pinning to specific versions) tends to work well enough on reasonably current code. Pipenv pretty much solves the problem by introducing a lockfile.
- m45t3r 8y agoWell, it impacts those people who needs their work, for example for validation of scientific experiments. It doesn't impact the ecosystem very much for sure, however I wouldn't say that the impact is zero.