Hacker News Reader

Comment by javchz | Hacker News Reader

Agree. I mostly do front end in my day job, and despite JavaScript being a bit of a mess lang, dealing with npm is way better than juggling anaconda, miniforge, Poetry, pip, venv, etc depending on the project.

UV is such a smooth UX that it makes you wonder how something like it wasn’t part of Python from the start.

View on HN

…but we did have to wait for cargo, npm (I include yarn and pnpm here) and maybe golang to blaze the ‘this is how it’s done’ trail. Obvious in hindsight.

Ruby's bundler had already invented the correct model many years ago. It only took time for others to accept that.

Wait, a bundler? What needs to be bundled when using Ruby? Maybe this is not the same meaning as with JS bundlers. And why does a bundles manage dependencies?

It’s what it’s called https://bundler.io/

No sillier than the other various package managers.

Yeah, but unlike bundle, uv locks in your Python version and downloads that Python version as needed. It’s like bundle and rbenv combined.

Sure. That seems less important to me than the packages. As long as the language version is checked, that’s the important bit.

More importantly, migrating from npm, to pnpm, to yarn, to bun, is very nearly seamless. Migrating in the Python ecosystem? Not anywhere close.

standardizing pyproject.toml helped but it didn't go quite far enough.

Feels like you're doing it wrong if you're dealing with all of those.

"depending on the project"

You mean off the job you have to juggle all those tools? On the job that would be kind of crazy, to allow every project its own tool chain.

Reply on news.ycombinator.com