I'm continuing to be amaxed at the astral team and what they do for Python. It's become so "bad" now that when I use Rust or OCaml I find myself constantly annoyed by the build systems. What a great time to be alive!
I was looking for Astral’s future plans to make money. Simonw already answered in another post [1] tldr - keep tooling open and free forever, build enterprise services (like a private package registry) on top.
What a great thing to see on HackerNews this morning. Any day I can replace another tool in my team’s processes with a fast, stable, and secure solution from Astral is a great day. Thanks Astral for all the amazing work you do!
People have been asking how Astral is going to monetize. Given the "AI" posts from Astral adjacent people, I'm now considering that they might release "AI" tools for an integrated "developing" workflow.
I really like using UV. I introduced it at work for builds and it made everything a lot faster which was awesome. Now I can remove the other components of the build process and just use one.
I am interested in how they're going to make money eventually, but right now it's working for me.
Does anyone have an idea about how they're going to monetize?
For years Python has been build on a skeleton crew.
Especially compared to billions poured into Javascript ecosystem due to it being native language of the web.
The money for Python was never there, even when it become the top language of data engineering and data science. Even now, devs that improve Python ecosystem get fired: https://bsky.app/profile/snarky.ca/post/3lp5w5j5tws2i
I've been coding in Python for 10+ years but I can never really get python's tooling ecosystem. It seems that there's always a newer shiny choice. easy_install, pip, conda, virtualenv, pipenv, setup_tools, hatchling, setuptools-scm, uv, requirements.txt, pyproject.toml...
I wish python can provide an "official" solution to each problem (like in rust, there's cargo, end of story), or at lease, an official document describing the current best practice to do things.
I tried installing a Python project last week after years of avoiding it like the plague.
brew install didn't work, use python3 not python, no pip pre-installed, ensurepip is crashing, you need to run sudo commands to fix this, after 1hour of struggle, repo didn't work anyway. how do people work like this?
uv has a super power that it doesn't much talk about - seamlessly managing monorepos. I'd been using pants before, but it's such a pain to setup and maintain. uv just kinda works like you'd hope.
20 comments
[ 4.4 ms ] story [ 31.0 ms ] threadWill it support the wide range of options setuptools does? Or maybe a build.rs equivalent - build.py, but in a sane way unlike setup.py.
[1] https://news.ycombinator.com/item?id=44358482
I am interested in how they're going to make money eventually, but right now it's working for me.
Does anyone have an idea about how they're going to monetize?
Makes me wonder, did the Python core team fail to see the opportunity in python tooling, have no desire to build it, or they didn't have the skills?
Especially compared to billions poured into Javascript ecosystem due to it being native language of the web. The money for Python was never there, even when it become the top language of data engineering and data science. Even now, devs that improve Python ecosystem get fired: https://bsky.app/profile/snarky.ca/post/3lp5w5j5tws2i
I wish python can provide an "official" solution to each problem (like in rust, there's cargo, end of story), or at lease, an official document describing the current best practice to do things.