I was talking about the maintainers not wanting to include features a lot of the userbase would like (like monorepo stuff), because they are saying their target audience is package authors, while in fact most of the users aren't.
Would be curious if anyone thinks this is a useful direction, ultimately hope uv/hatch include something like this.
the uv support on workspaces (virtual and concrete) has me intrigued.
Why does it work for FAANG but not for you?
Package A depends on C 1.0 and B depends on C 2.0. How much work it is to get down to one version of C in your dependencies is up to how different 1.0 & 2.0 is, and how A & B use it. But if you want them resolved, it's up to you to do the engineering to A or B.
if some smart and dedicated engineers can do the work to build a tool that lets everyone trivially manage a monorepo, that is certainly the best possible situation to end up in.
The shell scripts I wrote are a painful, but less painful than dealing with Bazel.