3 ms·
Really? The first release of pip was in 2011 [1] and the earliest release of Conda I can find is 1.1.0 in Nov. 2012 [2], and the first public commit (into an e
by mkl 6y ago
Really? The first release of pip was in 2011 [1] and the earliest release of Conda I can find is 1.1.0 in Nov. 2012 [2], and the first public commit (into an empty repo) was a month earlier [3].
[1] https://en.wikipedia.org/wiki/Pip_(package_manager) https://en.wikipedia.org/wiki/Pip_(package_manager)
[2] https://github.com/conda/conda/tags?after=1.3.0 https://github.com/conda/conda/tags?after=1.3.0
[3] https://github.com/conda/conda/commit/c9aea053d8619e1754b24b7283491b182a01dde8 https://github.com/conda/conda/commit/c9aea053d8619e1754b24b...
- mixmastamyk 6y agoMay be anaconda that I'm thinking of.
- dragonwriter 6y agoAnaconda was released in 2012, as well. Conda is a tool that is part of anaconda.
- mixmastamyk 6y agoThis one: https://en.wikipedia.org/wiki/Anaconda_(installer) https://en.wikipedia.org/wiki/Anaconda_(installer) I forgive myself, it's pretty confusing :D.
- dragonwriter 6y agoAh. Name collisions suck.
- mixmastamyk 6y agoEspecially when they conceptually do the same thing.
- JAlexoid 6y agoAnd that's another issue with Python ecosystem
- mixmastamyk 6y agoWhy do you think Python is more susceptible than other platforms? It is true that PyPi was designed before the author/project naming scheme popularized by github. Other than that I don't see a greater problem with name collisions in Python.
- JAlexoid 6y agoSusceptible - yes, all platforms could fall to this. That's why a strong leadership in a community, or subcommunities, works well. Python lacked this leadership, that leads to millions of half-arsed projects that compete... without moving the whole platform forward. It feels like NIH syndrome has permeated Python. Hopefully that's going to change