5 ms·

Maybe you could. I would stare longingly into the void, wondering if I can ever work another python project after having experienced uv, ruff, and ty. Such an

by tomrod 7mo ago

Maybe you could. I would stare longingly into the void, wondering if I can ever work another python project after having experienced uv, ruff, and ty. Such an outcome would make me wonder regarding the wisdom of "It is better to have love and lost than to have never loved at all."

giancarlostoro 7mo ago
It is an MIT licensed project, someone will absolutely fork it.
- WesolyKubeczek 7mo ago
  You seem to be underestestimating the laziness of the people, and overestimating their resolve. Angry forks usually don't last, angst doesn't prevent maintenance burnouts.
  - jitl 7mo ago
    clicking "fork" in github is pretty easy
    - WesolyKubeczek 7mo ago
      If you think clicking “fork” is all there is to it, I have some bad news for you.
  - giancarlostoro 7mo ago
    You underestimate the value that something like uv and company bring to the ecosystem. Given enough time I could have seen it replacing some core utilities, now that its owned by OpenAI I don't see that happening, unless OpenAI "donates" the project but keeps the devs on a payroll.
  - deleted 7mo ago
    [deleted]
signal11 7mo ago
I was using poetry pretty happily before uv came along. I’d probably go back. Note that uv is fast because — yes, Rust, but also because it doesn’t have to handle a lot of legacy that pip does[1], and some smart language independent design choices. If uv became unavailable, it’d suck but the world would move on. [1] https://nesbitt.io/2025/12/26/how-uv-got-so-fast.html https://nesbitt.io/2025/12/26/how-uv-got-so-fast.html
- theLiminator 7mo ago
  Maybe I could give up uv, but giving up ruff would suck.
  - crdrost 7mo ago
    This is just the weirdest thread. Like, the whole point of open source is that this thread is not a thing. The whole point is "if this software is taken on by a malevolent dictator for life, we'll just fork it and keep going with our own thing." Or like if I'm evaluating whether to open-source stuff at a startup, the question is "if this startup fails to get funding and we have to close up shop, do I want the team to still have access to these tools at my next gig?" -- there are other reasons it might be in the company's interests, like getting free feature development or hiring better devs, but that's the main reason it'd be in the employees' best interests to want to contribute to an open-source legacy rather than keep everything proprietary.
    - asa400 7mo ago
      The leadership and product direction work are at least as hard as the code work. Astral/uv has absolutely proven this, otherwise Python wouldn't be a boneyard for build tools. Projects - including forks - fail all the time because the leadership/product direction on a project goes missing despite the tech still being viable, which is why people are concerned about these people being locked up inside OpenAI. Successfully forking is much easier said than done.
      - PaulHoule 7mo ago
deadbabe 7mo ago
Maybe consider something other than python.
- scuff3d 7mo ago
  Good luck with that. I haven't been successful at convincing anyone to move away from it. I'm so fucking sick of writing Python at work lol
  - tomrod 7mo ago
    Why?
    - scuff3d 7mo ago
      Because I hate dynamically typed languages for anything besides scripting and glue code. Or are you asking why I haven't had success? Mostly because the people I work with are dead set that Python is perfect for everything. I had one guy argue it should be used for embedded work
  - Chris2048 7mo ago
    What would you prefer to use?
    - scuff3d 7mo ago
      Just about anything, as long as it's statically typed. The domain I work in is basically perfect for Go, so I've been pushing for that.
- tomrod 7mo ago
  Always choose the best tool for the job. Then import that tool and and check if __name__ == "__main__"
FreakLegion 7mo ago
Ruff is performant but finds about half the issues Pylint does (see https://github.com/astral-sh/ruff/issues/970 https://github.com/astral-sh/ruff/issues/970). Ty is quantitatively the worst of the well-known type checkers (see https://news.ycombinator.com/item?id=47398023 https://news.ycombinator.com/item?id=47398023). Uv is Astral's only winner.
- blazarquasar 7mo ago
  You are aware that ty has only recently entered beta status? Ruff isn’t stable yet either and has evolved into the de facto standard for new projects. It has more than double the amount of rules than Pylint does. Also downloaded more than 3 times as often as Pylint in the past month. Pylint has some advantages, sure, but Ruffs adoption speaks for itself. Pylint is 25 years old. You’d hope they do some things better. Saying that uv is their only winner is a hilarious take.
  - fud101 7mo ago
    >Saying that uv is their only winner is a hilarious take. na this news is good enough reason to move from Ruff back to black and stay the course, I won't use anything else from Astral. I will use uv but only until pip 2/++ gets its shit together and catches up and hopefully then as a community we should jump back on board and keep using pip even if it's not as good, it's free in the freedom sense.
  - FreakLegion 7mo ago
    Reread the comment I replied to: > I would stare longingly into the void, wondering if I can ever work another python project after having experienced uv, ruff, and ty. You think you're disagreeing with me, but you're agreeing. To wit: The original post is silly, because ty is beta quality and Ruff isn't stable yet either. Your words. These are just tools, Pylint included. Use them, don't use then, make them your whole personality to the point that you feel compelled to defend them when someone on the Internet points out their flaws. Whatever churns your butter.

by tomrod 7mo ago

giancarlostoro 7mo ago

It is an MIT licensed project, someone will absolutely fork it.

WesolyKubeczek 7mo ago
You seem to be underestestimating the laziness of the people, and overestimating their resolve. Angry forks usually don't last, angst doesn't prevent maintenance burnouts.
- jitl 7mo ago
  clicking "fork" in github is pretty easy
  - WesolyKubeczek 7mo ago
    If you think clicking “fork” is all there is to it, I have some bad news for you.
- giancarlostoro 7mo ago
  You underestimate the value that something like uv and company bring to the ecosystem. Given enough time I could have seen it replacing some core utilities, now that its owned by OpenAI I don't see that happening, unless OpenAI "donates" the project but keeps the devs on a payroll.
- deleted 7mo ago
  [deleted]

signal11 7mo ago

I was using poetry pretty happily before uv came along. I’d probably go back. Note that uv is fast because — yes, Rust, but also because it doesn’t have to handle a lot of legacy that pip does[1], and some smart language independent design choices. If uv became unavailable, it’d suck but the world would move on. [1] https://nesbitt.io/2025/12/26/how-uv-got-so-fast.html https://nesbitt.io/2025/12/26/how-uv-got-so-fast.html

theLiminator 7mo ago
Maybe I could give up uv, but giving up ruff would suck.
- crdrost 7mo ago
  This is just the weirdest thread. Like, the whole point of open source is that this thread is not a thing. The whole point is "if this software is taken on by a malevolent dictator for life, we'll just fork it and keep going with our own thing." Or like if I'm evaluating whether to open-source stuff at a startup, the question is "if this startup fails to get funding and we have to close up shop, do I want the team to still have access to these tools at my next gig?" -- there are other reasons it might be in the company's interests, like getting free feature development or hiring better devs, but that's the main reason it'd be in the employees' best interests to want to contribute to an open-source legacy rather than keep everything proprietary.
  - asa400 7mo ago
    The leadership and product direction work are at least as hard as the code work. Astral/uv has absolutely proven this, otherwise Python wouldn't be a boneyard for build tools. Projects - including forks - fail all the time because the leadership/product direction on a project goes missing despite the tech still being viable, which is why people are concerned about these people being locked up inside OpenAI. Successfully forking is much easier said than done.
    - PaulHoule 7mo ago

deadbabe 7mo ago

Maybe consider something other than python.

scuff3d 7mo ago
Good luck with that. I haven't been successful at convincing anyone to move away from it. I'm so fucking sick of writing Python at work lol
- tomrod 7mo ago
  Why?
  - scuff3d 7mo ago
    Because I hate dynamically typed languages for anything besides scripting and glue code. Or are you asking why I haven't had success? Mostly because the people I work with are dead set that Python is perfect for everything. I had one guy argue it should be used for embedded work
- Chris2048 7mo ago
  What would you prefer to use?
  - scuff3d 7mo ago
    Just about anything, as long as it's statically typed. The domain I work in is basically perfect for Go, so I've been pushing for that.
tomrod 7mo ago
Always choose the best tool for the job. Then import that tool and and check if __name__ == "__main__"

FreakLegion 7mo ago

Ruff is performant but finds about half the issues Pylint does (see https://github.com/astral-sh/ruff/issues/970 https://github.com/astral-sh/ruff/issues/970). Ty is quantitatively the worst of the well-known type checkers (see https://news.ycombinator.com/item?id=47398023 https://news.ycombinator.com/item?id=47398023). Uv is Astral's only winner.

blazarquasar 7mo ago
You are aware that ty has only recently entered beta status? Ruff isn’t stable yet either and has evolved into the de facto standard for new projects. It has more than double the amount of rules than Pylint does. Also downloaded more than 3 times as often as Pylint in the past month. Pylint has some advantages, sure, but Ruffs adoption speaks for itself. Pylint is 25 years old. You’d hope they do some things better. Saying that uv is their only winner is a hilarious take.
- fud101 7mo ago
  >Saying that uv is their only winner is a hilarious take. na this news is good enough reason to move from Ruff back to black and stay the course, I won't use anything else from Astral. I will use uv but only until pip 2/++ gets its shit together and catches up and hopefully then as a community we should jump back on board and keep using pip even if it's not as good, it's free in the freedom sense.
- FreakLegion 7mo ago
  Reread the comment I replied to: > I would stare longingly into the void, wondering if I can ever work another python project after having experienced uv, ruff, and ty. You think you're disagreeing with me, but you're agreeing. To wit: The original post is silly, because ty is beta quality and Ruff isn't stable yet either. Your words. These are just tools, Pylint included. Use them, don't use then, make them your whole personality to the point that you feel compelled to defend them when someone on the Internet points out their flaws. Whatever churns your butter.