a_bored_husky

Hello from Cuba. We do have internet and modern computers.

> 1. It tries to do too many things. Please just do one thing and do it well. It's simultaneously trying to replace pip, pyenv, virtualenv, and ruff in one command.

I think there are more cases where pip, pyenv, and virtualenv are used together than not. It makes sense to bundle the features of the three into one. uv does not replace ruff.

> 2. You end up needing to use `uv pip` so it's not even a full replacement for pip.

uv pip is there for compatibility and to facilitate migration but once you are full on the uv workflow you rarely need `uv pip` if ever

> 3. It does not play well with Docker.

In what sense?

> 4. It adds more complexity. You end up needing to understand all of these new environmental variables: `UV_TOOL_BIN_DIR`, `UV_SYSTEM_PYTHON`, `UV_LINK_MODE`, etc.

You don't need to touch them at all

Cuba

1/100 of that is life changing money for most people here in my country. I can't imagine...

Thank you.

This is awesome. My wish is to one day be in a position to do things like this and help people in need.

Thank you.

> as long as you tune things correctly

Can you elaborate?

Even less job oportunities, sadly.

They were right tho.

Discourse, not Discord.

The mirroring part is for the rss feed specifically. When a podcast is added to the website a feed is generated with the same data as the original feed but only including the processed episodes and the media links pointing to our files. Then you subscribe to that feed instead of the original using your favorite podcasts app.

We have some "hidden" features like subscribing to a tag or merging many podcasts in one feed, but nothing time related.