8 ms·
same for uv but no one takes that message. They just think "rust rulez!" and ignore that all of uv's benefits are algo, not lang.
by socalgal2 7mo ago
same for uv but no one takes that message. They just think "rust rulez!" and ignore that all of uv's benefits are algo, not lang.
- estebank 7mo agoSome architectures are made easier by the choice of implementation language.
- crubier 7mo agoIn my experience Rust typically makes it a little bit harder to write the most efficient algo actually.
- catlifeonmars 7mo agoThat’s usually ok bc in most code your N is small and compiler optimizations dominate.
- Defletter 7mo agoWould you be willing to give an example of this?
- lukeweston1234 7mo agoNot OP, but one example where it is a bit harder to do something in Rust that in C, C++, Zig, etc. is mutability on disjoint slices of an array. Rust offers a few utilities, like chunks_by, split_at, etc. but for certain data structures and algorithms it can be a bit annoying. It's also worth noting that unsafe Rust != C, and you are still battling these rules. With enough experience you gain an understanding of these patterns and it goes away, and you also have these realy solid tools like Miri for finding undefined behavior, but it can be a bit of a hastle.
- catlifeonmars 7mo agoHas no one written a python! macro for this use case?
- foldr 7mo agoMutating tree structures tends to be a fiddle (especially if you want parent pointers).
- EdwardDiego 7mo agoUV also has the distinct advantage in dependency resolution that it didn't have to implement the backwards compatible stuff Pip does, I think Astral blogged on it. If I can find it, I'll edit the link in. edit wasn't Astral, but here's the blog post I was thinking of. https://nesbitt.io/2025/12/26/how-uv-got-so-fast.html https://nesbitt.io/2025/12/26/how-uv-got-so-fast.html That said, your point is very much correct, if you watch or read the Jane Street tech talk Astral gave, you can see how they really leveraged Rust for performance like turning Python version identifiers into u64s.
- rowanG077 7mo agoThat's a pretty big claim. I don't doubt that a lot of uv's benefits are algo. But everything? Considering that running non IO-bound native code should be an order of magnitude faster than python.
- thfuran 7mo agoMore than one, I'd think.
- jeremyjh 7mo agoIts a pretty well-supported claim. uv skips doing a number of things that generate file I/O. File I/O is far more costly than the difference in raw computation. pip can't drop those for compatibility reasons. https://nesbitt.io/2025/12/26/how-uv-got-so-fast.html https://nesbitt.io/2025/12/26/how-uv-got-so-fast.html
- rowanG077 7mo agoI don't think the article you linked supports the claim that none of UV performance improvements are related to using rust over python at all. In fact it directly states the exact opposite. They have an entire section dedicated to why using Rust has direct performance advantages for UV.
- jeremyjh 7mo agoWhat it says is this: > uv is fast because of what it doesn’t do, not because of what language it’s written in. The standards work of PEP 518, 517, 621, and 658 made fast package management possible. Dropping eggs, pip.conf, and permissive parsing made it achievable. Rust makes it a bit faster still.
- rowanG077 7mo agoYes exactly! That quote directly disproves that all of the improvements UV has over competitors is because of algos, not because of rust. So the claim is not well supported at all by the article as you stated, in fact the claim is literally disproven by the article.
- coldtea 7mo agoJust the fact that I can install a single binary is 10x better than an equally fast Python implementation.