Live data from Hacker News

Uv is the best thing to happen to the Python ecosystem in a decade

emily.space

881–890 of 1001 posts

Re: Uv is the best thing to happen to the Python ecosystem in a decade

#881
post #872

Earlier quoted context omitted.

It is open source. If they enshitify UV with monetization, it will be forked.

Yes, but only after fracturing the ecosystem even further unfortunately.

Anaconda is a good example of this.

Re: Uv is the best thing to happen to the Python ecosystem in a decade

#882

I predict it'll be the best and then the 'worst' thing: they'll go hard on monetisation. Just look at this post: 1839 points and 1048 comments! That is insane. It's captured the hearts and minds of Python devs and I'm sure they know it. I'm not against projects making money, just remember you'll likely pay a price later on once you invest in more of Astral's ecosystem. It's just temporarily free.

It is open source. If they enshitify UV with monetization, it will be forked.

Most forks eventually die.

Re: Uv is the best thing to happen to the Python ecosystem in a decade

#883
post #843

I predict it'll be the best and then the 'worst' thing: they'll go hard on monetisation. Just look at this post: 1839 points and 1048 comments! That is insane. It's captured the hearts and minds of Python devs and I'm sure they know it. I'm not against projects making money, just remember you'll likely pay a price later on once you invest in more of Astral's ecosystem. It's just temporarily free.

They’ve been very transparent about their monetization strategy and it does not impact uv’s foss model

Until they change their minds. If they were serious about it, it would be part of PyCQA

Re: Uv is the best thing to happen to the Python ecosystem in a decade

#884

Uv is so good. I'm a curmudgeon about adopting new tooling, and tried uv with a lot of skepticism, but it was just better in every way. And even if it wasn't so polished and reliable, the raw speed makes it hard to go back to any other tool. Uv combined with type hints reaching critical mass in the Python ecosystem, and how solid PyLance is in VSCode, feels so good it has made me consider investing in Python as my pr…

> But then I remember that Python is dog slow compared to other languages with comparable ergonomics and first-class support for static typing, and...idk it's a tough sell. Case in point: uv itself is not written in Python. It's a Rust tool. It always amazes me when people work on an ecosystem for a language but then don't buy enough into that to actually use it to do the work. Avoidance of dogfooding is a big red fl…

Interpreted languages are not the best choicce for a variety of software. for eg: Vast amount of performance issues in typescript cli boil down to being written in typescript, and team is porting to golang now.

Tools specifically CLI tools, are best written in statically typed compiled languages.

Re: Uv is the best thing to happen to the Python ecosystem in a decade

#885

I have to say that I am extremely reluctant to switch over to yet another python management system (packaging, environment, python version). Every few years someone says: this is it. Switch to poetry! Okay, I did. And, at least for some academic packages, psychopy I'm looking at you, it was a friggin disaster. so. will uv install psychopy (say version 3.2.4)?

Well... I did pip -> poetry -> rye -> uv in less than a year, so I can understand the fatigue. But the fact is that uv is well above the rest and was well worth the effort (and the wait).

Re: Uv is the best thing to happen to the Python ecosystem in a decade

#886
post #58

I hadn't paid any attention to rust before uv, but since starting to use uv, I've switched a lot of my performance-sensitive code dev to rust (with interfaces to python). These sorts of improvements really do improve my quality of life significantly. My hope is that conda goes away completely. I run an ML cluster and we have multi-gigabyte conda directories and researchers who can't reproduce anything because just to…

I work professionally in ML and have not had to touch conda in the last 7 years. In an ML cluster, it is hopefully containerized and there is no need for that?

> I work professionally in ML and have not had to touch conda in the last 7 years. In an ML cluster, it is hopefully containerized and there is no need for that?

I wish my life had been like this. Unfortunately I always appear to end up needing to make this stuff work for everyone else (the curse of spending ten years on Linux, I suppose).

But then ML is a very broad church, and particularly if you're a researcher in a bigger company then I could see this being true for lots of people (again, i wish this was me).

Re: Uv is the best thing to happen to the Python ecosystem in a decade

#887

>curl -LsSf https://astral.sh/uv/install.sh | sh Don't do this shit, especially if you were told to do this shit. If you are going to do this shit, separate the commands, read the bash script (and roll it down, if another file is downloaded, download that manually and inspect it). If you are going to ask people to do this shit, split the command into two. Someone that asks me to do something insecure is either a mali…

Nobody actually inspects binaries anyway, what's the difference?

Re: Uv is the best thing to happen to the Python ecosystem in a decade

#888
post #843

Earlier quoted context omitted.

They’ve been very transparent about their monetization strategy and it does not impact uv’s foss model

Until they change their minds. If they were serious about it, it would be part of PyCQA

The same PyCQA that they worked hard to do a significantly better job than?

Re: Uv is the best thing to happen to the Python ecosystem in a decade

#889
post #58

I hadn't paid any attention to rust before uv, but since starting to use uv, I've switched a lot of my performance-sensitive code dev to rust (with interfaces to python). These sorts of improvements really do improve my quality of life significantly. My hope is that conda goes away completely. I run an ML cluster and we have multi-gigabyte conda directories and researchers who can't reproduce anything because just to…

As a person who has successfully used uv for ml workloads, I'm curious what makes you still stay with Conda.

Conda is much, much better for the C/Fortran/C++ parts of data science/machine learning workloads.

Like, I had real issues with GDAL and SQLite/spatialite on MacOS (easy on Linux) which uv was of no help with. I ended up re-architecting rather than go back to conda as uv is just that good (and it was early stage so wasn't that big of a deal).

Post reply on HN