Uv's killer feature is pulling in local dependencies

Re:Uv's killer feature is pulling in local dependencies by tehjoker on Sunday January 12, 2025 @03:57PM (#42676863)

What is the deal with uv's ownership policy? I heard it might be VC backed. To my mind, that means killing pip and finding some kind of subscription revenue source which makes me uneasy.

The only way to justify VC money is a plot to take over the ecosystem and then profit off of a dominant position. (e.g. the Uber model)

I've heard a little bit about UV's technical achievements, which are impressive, but technical progress isn't the only metric.

[ Parent | on HN ]

Re:Uv's killer feature is pulling in local dependencies by feznyng on Sunday January 12, 2025 @07:30PM (#42678614)

It’s dual MIT and Apache licensed. Worst case, if there’s a rug pull, fork it.

[ Parent | on HN ]

Re:Uv's killer feature is pulling in local dependencies by tehjoker on Sunday January 12, 2025 @10:13PM (#42679697)

Is that the entire story? If so the VCs are pretty dumb. If they kill pip, that means the people who were maintaining it disperse and forking it won't restore the ecosystem that was there before.

[ Parent | on HN ]

Re:Uv's killer feature is pulling in local dependencies by feznyng on Monday January 13, 2025 @03:39PM (#42688869)

Yarn and pnpm didn’t kill npm. I don’t see how pip could ever be fully supplanted by uv. And if it is, that would probably mean the python foundation is stewarding it.

[ Parent | on HN ]