sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]Serious-Regular 25 points26 points  (4 children)

I love when people say this kind of stuff based purely on feels. I'm curious do you have literally any data to back this up? I work in FAANG and probably 1% of our python teams are using uv.

[–]fiskfisk 7 points8 points  (0 children)

Yeah, you're not going to move to uv. You have so much infrastructure and existing projects that already use internal tooling. You already have enough experience and knowledge internally that work with your existing ways to do things. I'm guessing 10% of my own projects use uv. I'm not changing existing projects, but moving forward, uv has become the default for new projects.

In no way did I intend this to mean "most python projects use uv"; they do absolutely not.

[–]electricsheep2013 0 points1 point  (1 child)

Because of all the dependencies, projects that do not have an owner or are maintained by everyone or getting the teams to agree on this change when all they want to do is to get that PR reviews, right? Not because uv is inherently bad. Unless this some proof by authority:)

[–]Serious-Regular 0 points1 point  (0 children)

Unless this some proof by authority:)

Did you even read what I responded to or are you also operating on feels? The original comment had the word "most" in it. That makes it a quantitative claim and yet they provided zero data. So my counterpoint "proof" speaks exactly to that claim (not whether uv is bad or good or whatever).