The uv build back end is now stable

The comments in this thread all feel like auto generated engagement bot replies you'd see on twitter.

Building tooling in Rust? Blasphemy! You should have used Node.js, because teaching Rust to people is too hard! And it's not doing any CPU heavy computations anyway, so Node.js is fine!

Bots don't make that much spelling mistakes. Bots as in LLMs not people paid to engage.

My good uv experience. I tried installing tensor/cuda Python code recently. Plain pip just failed. uv pip actually returned WHY it failed.

It definitely felt like magic.

No. You must rewrite it in Zig. Or C like a real man. Or if you're Chuck Norris just look at computer angrily.

donkey_brains definitely looks to have low karma, the rest of the comments seem legit.

I'd think the same, but I agree with all the comments.

I know ! the problem is that when a product is so good that it converts people into evangelicals about it

With that said — it’s uv or die for me

There's rather too many gleeful exclamation marks. Here's a rare case where a karmascope would be useful; I see https://news.ycombinator.com/user?id=the_mitsuhiko has 15025 karma, so they're almost certainly real.

I’ve been using and advocating uv ever since forever. It’s impossible to think about using python without nowadays.

Among many things it’s improved, scripting with python finally just works without the pain of some odd env issue.

I wouldn't be so sure about spelling mistakes. Even before LLMs, YouTube bots made a lot of mistakes (probably because gives the impression that it's a human typing). Currently, it's impossible to distinguish between a human and LLM comment.

unlike ruff, uv doesnt benefit that much from being written in rust.

its main benefit is that it is well maintained and does everything you used to need a string of tools for before.

>Bots don't make that much spelling mistakes.

They do if you instruct them to.

Oh that's so very false!

---

time uv

real 0m0.005s

user 0m0.000s

sys 0m0.004s

---

time npm

real 0m0.082s

user 0m0.068s

sys 0m0.020s

---

time pip

real 0m0.320s

user 0m0.179s

sys 0m0.031s

> Among many things it’s improved, scripting with python finally just works without the pain of some odd env issue.

From what I can tell uv doesn’t (unlike poetry) assist with venvs what so ever.

What is a trivial «poetry run» becomes the same venv-horrors of Python fame when I use uv and «uv run».

Based on that, your comment strikes me as the polar opposite of my experience (which is why I still resort to poetry).

Care to outline how you use v to solve venv-issues, since from what I can tell, uv explicitly doesn’t?

I’m very curious.

I use uv in my shebang and “uv run script.py”. Never run into any issues.

Here’s a couple links to discussions about it on HN:

https://news.ycombinator.com/item?id=42198256

https://news.ycombinator.com/item?id=42855258

Interesting that this was pushed to the bottom of the replies (despite being at the top at 20 upvotes). Did all the above comments get a coordinated signal to upvote beyond that number, or is a HN mod compromised?

So if you've imported pytest and want to run it, you can’t just «uv run pytes», but have to create a script with a uv-shebang which runs pytest for you?

And how does that work on Windows, which to my knowledge doesn’t even support shebangs?

lol i dont think people are switching because they save 255 milliseconds per command line run.

Why would you want them to make spelling errors? The benefits don't outweigh the costs.

If the intention is "increase believability a real human wrote this bot message" they do

Sure but adding error rate also makes it so you trust the speaker less, because they aren't educated enough or ESL.