Live data from Hacker News

Uv saves Home Assistant 215 compute hours per month

developers.home-assistant.io

11–20 of 60 posts

Re: Uv saves Home Assistant 215 compute hours per month

#11
post #9
post #8

Earlier quoted context omitted.

uv isn't a performance improvement on pip but a ground-up rewrite in a completely different language.

Source on the logic being different from pip? Last I checked it's nothing more than a port of pip to rust.

I’m unclear on how you “port” a library from Python to Rust, it’s a ground up rewrite with a familiar interface to pip but fundamentally doesn’t share any code.

Re: Uv saves Home Assistant 215 compute hours per month

#13

So .. like ... Why not dump python entirely if you are doing a python to rust port of a core aspect of python tool gain?

Changing your build tool to another tool (designed to be a drop-in replacement) is very different from changing your entire codebase...

Re: Uv saves Home Assistant 215 compute hours per month

#15
post #4

Would the authors not have been better off adding their performance improvements to pip rather than creating their own tool? I remember this being a complaint from Node maintainers when Bun was released: they had multiple open performance-related issues with no one available to work on them.

I’m guessing “rewrite it in Rust” would have been an unpalatable PR for the pip maintainers to merge.

Yeah but I suspect there’s something more going on than Rust magic. They’re claiming a savings of about an hour and a half. (4% of the original time) That sounds like an architecture change, or more likely a whole lot of caching.

Re: Uv saves Home Assistant 215 compute hours per month

#17

So .. like ... Why not dump python entirely if you are doing a python to rust port of a core aspect of python tool gain?

Well because best tool for the job. There is no natural law that everything must be bootstrapped. Languages use LLVM for example.

Re: Uv saves Home Assistant 215 compute hours per month

#18

Every time I hear "new system faster than old system!", my first thought is: what features does the new system not implement, what corner-cases does it ignore? What are the trade-offs?

Rust, the language, has rather successfully worked towards and demonstrated that, in many areas, you CAN have your pie and eat it too. But that doesn't carry over to applications, where it must be demonstrated again.

Re: Uv saves Home Assistant 215 compute hours per month

#19
post #9
post #8

Earlier quoted context omitted.

uv isn't a performance improvement on pip but a ground-up rewrite in a completely different language.

Source on the logic being different from pip? Last I checked it's nothing more than a port of pip to rust.

It is not.

> Limitations

> While uv supports a large subset of the pip interface, it does not support the entire feature set. In some cases, those differences are intentional; in others, they're a result of uv's early stage of development.

> For details, see our pip compatibility guide[1]

> Like pip-compile, uv generates a platform-specific requirements.txt file (unlike, e.g., poetry and pdm, which generate platform-agnostic poetry.lock and pdm.lock files). As such, uv's requirements.txt files may not be portable across platforms and Python versions.

[1] - https://github.com/astral-sh/uv/blob/main/PIP_COMPATIBILITY....

Post reply on HN