Re:Uv: Python packaging in Rust
by anze3db on Thursday February 15, 2024 @03:41PM
(#39388486)
I hope they answer this ASAP. People in the Python community are already concerned that Astral is following the Embrace, extend, and extinguish playbook.
[ Parent
| on HN ]
If all they did right now was leave Ruff exactly as it was and walk away they would have given the Python community a great gift.
Sure, it’s rendered a bunch of projects obsolete, but it’s because it’s so much better than the predecessors.
If they stop development on Ruff today, Ruff won't be useful anymore after a few new Python releases. If the maintainers of the tools that Ruff is replacing stop maintaining them, the whole Python community will be in a really bad place. So, there is reason to be cautious. Astral being transparent on how they plan to make money would be very helpful.
I do get the caution, but I think that even in that case there’s enough momentum behind Ruff for the community to fork and carry on.
Obviously it would be pretty crummy to end up in a situation like pyright where MS really have leant in to their embrace, extend, extinguish strategy.
Re:Uv: Python packaging in Rust
by the_mitsuhiko on Thursday February 15, 2024 @04:59PM
(#39389668)
> If they stop development on Ruff today, Ruff won't be useful anymore after a few new Python releases
That is true for every single development tool in the Python space.
Re:Uv: Python packaging in Rust
by theLiminator on Thursday February 15, 2024 @06:11PM
(#39390584)
People could just fork it if that happens. Since the foundation of the tooling is solid, I 'm sure the community would rally around a fork that keeps it going.
Re:Uv: Python packaging in Rust
by cqqxo4zV46cp on Thursday February 15, 2024 @04:04PM
(#39388836)
“People in the Python community”?
Yeah. Probably precisely the same people that call everything EEE.
You’ll always find people acting alarmist about anything.