logoalt Hacker News

evikslast Thursday at 6:13 PM3 repliesview on HN

The same things that prevented "community" from building the tool in the first place


Replies

PaulHoulelast Thursday at 8:04 PM

i think the main problem was that people didn't believe that pip was broken, or didn't think there was any value in a 100% correct package manager over a 97% correct package manager (e.g. misread "worse is better")

I had the problem basically understood in 2018 and I am still pissed that everybody wanted to keep taking their chances with pip just like they like to gamble with agent coders today.

Now that people know a decent package manager is possible in Python I think there is going to be no problem getting people to maintain one.

show 1 reply
zemlast Thursday at 6:39 PM

that makes zero sense to me. developing something like ruff from scratch takes a lot of things happening - someone having the idea, the time to develop it from scratch in their free time, or the money to do it as a job, and perhaps the need to find collaborators if it's too large a project for one person. but now ruff is there, there's no need to build it from scratch. if I wanted to build a python linter or formatter I would simply fork ruff and build on top of it. as others have said in this subthread, that's the whole point of open source!

show 1 reply
johnisgoodlast Thursday at 6:16 PM

Cannot we at one point consider the tool to be "done"? I mean, what is there to constantly change and improve? Genuinely curious. It sounds like a tool that can be finished. Can it not be?

show 2 replies