Thanks for the detailed analysis.
I’m wondering if you factored in the cost of engineering time invested in this analysis, and how that affects the payback time (if at all).
I gave a talk about this at the Packaging Summit during Pycon which was well received, so the team is definitely aware of the problem.
However, the sense I got was that it was going to be a lot of work to “fix Python packaging” which wasn't feasible with an all-volunteer group.
At work, we're migrating away from pip as a distribution mechanism for this reason; I don't expect to see meaningful improvements to the developer experience anytime soon.
This is especially true because pip today is roughly where npm was in 2015, so there's a lot of fundamental infrastructure work (including security) that still needs to happen.
An example of this is that PyPI just got the ability to namespace packages.
I'm curious if you're planning to turn Meltano Cloud into a managed ELT solution.
The FAQ at the bottom of the pricing page[1] describes Meltano Cloud as an EL solution, but the docs for open-source Meltano[2] highlight that it's an ELT tool.
> DuckDB is indeed a free columnar database system, but it is not entirely built on top of SQLite. It exposes the same front-end and uses components of SQLite (the shell and testing infrastructure), but the execution engine/storage code is new.