Remember, people. When a tool is:
⁃ open source
⁃ built to conform to open specifications
⁃ not coupled to a service offering

It does not matter who buys the company that built the tool

@offby1 My concern is more that the suite of projects in question only had such a high level of velocity, maintained-ness and polish because people were literally being paid, as their job, to do it. Once the money dries up, even the best-case outcomes still probably involve huge drop-offs in all those attributes due to the switch from "this is my job" to "this is my side/hobby project".
@ubernostrum Totally valid in terms of what future development will look like, but only barely relevant in terms of what's already there... and what's already there is a phenomenal upgrade to the python packaging experience.
@offby1 I feel like a lot of the credit given to uv actually belongs to the broader Python packaging community for working out the necessary standards to actually improve things; uv just was able to rapidly adopt and implement because it was literally someone's job (several someones) to do so. Compare to pip, where I know from personal experience that it's a struggle to get implementation of crucial new standards because it's a side project that has to fight for time even when funding is on offer.

@ubernostrum I agree with that formulation.

Again, the reaction I'm pushing back on is the one where people are (and I am not exaggerating here) saying python packaging is doomed now.

That's just not reasonable or realistic.

It's unlikely to improve as fast and consistently, but it is not doomed, and I wish that people would not react as though this was undoing what they've done that was good.