poetry vs uv?

[UltiRequiem]

I've been a devoted Poetry user for my Python projects for years, appreciating its dependency resolution, virtual environment management, and the simplicity of its pyproject.toml configuration. However, I've been experimenting with UV lately (the Rust-based package manager), and the speed difference is honestly jarring - package installations and dependency resolutions that took minutes now take seconds.

This has me at a crossroads regarding my workflow and tooling choices, and I'm hoping the Poetry maintainers might share their perspective:

Current Status: Is Poetry considering any Rust-based components or performance optimizations to address the speed gap? I understand the "Python-native" approach has advantages for extensibility and community contribution, but the performance difference is becoming hard to ignore.

Philosophical Question: What would you say are the core advantages of Poetry that would justify its continued use in a world where UV exists? Is it primarily the mature ecosystem, the publishing workflow, or something deeper about Poetry's design philosophy?

Future Vision: Does the team see Poetry and UV as fundamentally competing solutions, or is there a vision for how they might coexist in the Python ecosystem? Perhaps with Poetry focusing on project management and publishing while delegating installation to faster engines?

I'm asking this genuinely because I value Poetry's thoughtful approach to Python project management, but I'm struggling to justify the performance tradeoff in larger projects. Rather than just jumping ship, I'd love to understand how the maintainers see Poetry's place in this evolving landscape.

[dimbleby]

IMO this does not need to be a Philosophical Question: just use whatever tool best fits your needs, or that you like best. If that's poetry or uv or whatever - it's all good.