Uv saves Home Assistant 215 compute hours per month
developers.home-assistant.io
Uv saves Home Assistant 215 compute hours per month
1–10 of 60 posts
Re: Uv saves Home Assistant 215 compute hours per month
#2Would 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.
Re: Uv saves Home Assistant 215 compute hours per month
#3Would 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.
Most innovations happens outside large organizations, then either replaces it or the ideas get stolen/absorbed into the parent. All the downsides and barriers of operating in a large legacy system are pretty well known, even if the maintainers are receptive, radical change will be DOA.
Re: Uv saves Home Assistant 215 compute hours per month
#4Would 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.
Re: Uv saves Home Assistant 215 compute hours per month
#5Would 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.
It's tricky to change up some parts of pip because it might break some existing users flows. It's really hard to test for this kind of infrastructure tool because it's so environment-dependent. The rewrite lets there be a clean slate. Meanwhile the target of being "compatible" with pip gives them a good idea of where to go, and they can focus a bit more on testing given the lessons learned.
Re: Uv saves Home Assistant 215 compute hours per month
#6Would 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 think now their current positioning is that the competition actually helped demonstrate the value of some kinds of speed, and that finally got those performance issues prioritized enough to work on by people with the right knowledge. Node doesn't lack for people who want to contribute, its more about people who -can- contribute well, and yes as other comment noted, its often to easier to try things out outside the system rather than work within it.
Re: Uv saves Home Assistant 215 compute hours per month
#7Would 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 "lets rewrite in Rust" has become a meme with negative connotations that will attract ridiculed or be ignored, but Rust clearly excels in this sort of tooling. Whether it makes sense to rewrite an existing codebase or pigeonhole it on the edges is another question.
Re: Uv saves Home Assistant 215 compute hours per month
#8Would 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.
uv isn't a performance improvement on pip but a ground-up rewrite in a completely different language.
Re: Uv saves Home Assistant 215 compute hours per month
#9Would 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.
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.
Re: Uv saves Home Assistant 215 compute hours per month
#10So .. like ... Why not dump python entirely if you are doing a python to rust port of a core aspect of python tool gain?