I know it sa toy, but if someone gets the bright idea to do this for real: please learn from npm and dont duplicate packages for every clone of a project. Share them between projects like every sane package manager.
Before uv there was poetry, and before poetry there was pipenv, before pipenv there was virtualenv. I wish people would stop portraying Python tooling completely wrong like that. uv is not the first tool to solve most problems in this space. It may be the best performing though and may be the best overall currently.
I think you’re underselling it. You’ve listed several projects with many thousand man hours in development.
It’s telling that in Python there have been multiple package managers over the years to fix the broken status quo. Typescript/Javascript notwithstanding, in other languages and environments you get the one tool that’s been there for over a decade without competitors.
Very few languages have suffered from the same package manager issues as JS/TS and Python.
Virtual venv existed before uv. So you could still just generate a virtual venv and then use pip to install packages in the local venv. (2007: virtualenv was released as a third-party tool).
You don't want to install all dependencies globally. You only want to cache them globally. Each project should resolve its own dependency tree independently. If the wanted version is already in cache, use that, otherwise download from the repository even if an older / newer version is present in cache (unless the user specifically says to use the cache only). As long as your dependencies are inert (they don't mess with the system just by being present), this will work perfectly fine.
For non-inert packages, such as applications installed via the language's dependency manager, that's a different use case and should be handled differently.
That is the starting point though , minimum you need to buy one more for FO/DR if you care about uptime .
It is not once and done you have some continuous costs in either direction.
1. you will not be able to still move all your workloads only your base loads .
2. There will be residual workloads not only if they are spot/flexible bursts but also they are too deeply integrated to Paas offerings .
3. you have to pay for power cooling and network (and its backup) for 5 years .
4. Finally you also have pay for infra team to maintain, this is increasingly difficult (and expensive) to hire and retain .
Don’t get me wrong I would love to be able buy something like this, but the cost economy is pretty steep and 1-2M spends is too early (it is not on oxide, serious hardware costs a ton these days )
Reddit doesnt work because subreddits crosspolinate and float to the top so theyre rather prone to brigading and intermingling. We don't really get distinct subreddits anymore.
I think models will be a commodity sooner rather than later. This whole race doesnt matter. First mover advantage is real, but over enough time it wont matter.
Yes. Make sure you’re not using the Gemma sparse models since they don’t have a small model to use. Also I removed all the image models from the workspace.
All 4 gemma-4-*-it models, regardless whether they are dense models or MoE models, have associated small models for MTP, whose names are obtained by adding the "-assistant" suffix.
reply