Live data from Hacker News

Astral to Join OpenAI

astral.sh

621–630 of 951 posts

Re: Astral to Join OpenAI

#621

Earlier quoted context omitted.

Finally someone competent to answer the crucial question. Taken into account the enormous amount of excellent work you did, and the fact that dev tools are hard to monetize, what was your strategy?

You can find some resources on our strategy in previous blog posts, like this one on pyx[1]. [1]: https://astral.sh/blog/introducing-pyx

Are you going to join codex team as well? I am curious about how the codex code base will evolve after you guys joined. It is going to affect Python/Rust toolchains tremendously.

Re: Astral to Join OpenAI

#622

Earlier quoted context omitted.

It’s a small tool shop building a tiny part of the Python ecosystem, let’s not overstate their importance. They burned through their VC money and needed an exit and CLI tool chains are hyped now for LLMs, but this mostly sounds like an acquihire to me. Dev tools are among the hardest things to monetize with very few real winners, so good for them to get a good exit.

They were hyped here without any pushback. Maybe OpenAI thinks the Astral folks will now evangelize and foist Codex and ChatGPT onto the open source "community". People need to be very careful about resisting. OpenAI wants to make everyone unemployed, works with the Pentagon, steals IP, and copyright whistleblowers end up getting killed under mysterious circumstances.

given that they delivered the goods I would not say they were "hyped"

Re: Astral to Join OpenAI

#623

Earlier quoted context omitted.

Maybe I'm reading wrong here, but what's the implication of the clean room re-implementations? Someone else is cloning with a changed license, but if I'm still on the GPL licensed tool, how am I "not protected"?

1. Company A develops Project One as GPLv3 2. BigCo bus Company A 3a. usually here BigCo should continue to develop Project One as GPLv3, or stop working on it and the community would fork and it and continue working on it as GPLv3 3b. BigCo does a "clean-room" reimplementation of Project One and releases it under proprietary licence. Community can still fork the older version and work on it, but BigCo can continue t…

As a real world example, Redis was both Company A and BigCo. Project One is now ValKey.

Re: Astral to Join OpenAI

#624
post #95

Not who I would've liked to acquire Astral. As long as OpenAI doesn't force bad decisions on to Astral too hard, I'm very happy for the Astral team. They've been making some of the best Python tooling that has made the ecosystem so much better IME.

If Codex’s core quality is anything to go by, it’s time to create a community fork of UV

At least it’s in rust.

Unlike those react-game-engine guys over at Claude

Re: Astral to Join OpenAI

#625

Earlier quoted context omitted.

MS is actively making your life using VS Codium a pain. They removed the download button the extension marketrplace making it very difficult to download extensions and installing them in VS Codium since VS Codium does not have access to the official MS extension marketplace. Many don't publish outside the marketplace for example Platformio. [1] [1] https://github.com/platformio/platformio-vscode-ide/issues/1...

Also, Microsoft does not allow use of their LSP for python. You have to use the barebones Jedi LSP.

Fortunately, there are competing LSPs of reasonable quality now. I'm using pyrefly. Not sure if ty/ruff have one too.

Re: Astral to Join OpenAI

#626
post #320

Welp. I used to respect Astral. I hope someone responsible forks their Python tooling and maintains it. Ideally a foundation rather than a company.

Yeah, well, the fact is that every person who ever touches Python needed uv, but only Astral folks created it. So, nope, there's no one capable of filling the void, just accept that it's fucked now. The best die first.

I write python all the time and I've never used it

Re: Astral to Join OpenAI

#627
post #414

What strikes me most about this acquisition isn't the AI angle. It's the question of why so many open source tools get built by startup teams in the first place. I maintain an open source project funded by the Sovereign Tech Fund. Getting there wasn't easy: the application process is long, the amounts are modest compared to a VC round, and you have to build community trust before any of that becomes possible. But the…

open source allows you to build community trust must faster, and community trust/adoption is key

I don't see any betrayal here, since the tools are still OSS - yeah OpenAI might take it a different direction and add a bunch of stuff I don't like/want, but I can still fork

Re: Astral to Join OpenAI

#629
post #105

This has me thinking about VS Code and VS Codium. I've used VS Code for a while now, but recently grew annoyed at the increasingly prevalent prompts to subscribe to various Microsoft AI tools. I know you can make them go away, but if you bounce between different systems, and particularly deal with installing VS Code on a regular basis, it becomes annoying. I started using VS Codium, and it feels like using VS Code be…

I really wanted to use vscodium but had to go back to vscode proper because the remote ssh extension is just nowhere near as good. The open source one uses a JS library to implement the SSH protocol rather than using a system binary which means many features (GSSAPI) aren't supported. Also just seems like a bad idea to use an SSH implementation that's not nearly as battle tested as openssh...

Re: Astral to Join OpenAI

#630
post #292

Earlier quoted context omitted.

Same. It's game-changing - leaps and bounds above every previous attempt to make Python's packaging, dependency management, and dev workflow easy. I don't know anyone who has tried uv and not immediately thrown every other tool out the window.

I use uv here and there but have a bunch of projects using regular pip with pip-tools to do a requirements.in -> requirements.txt as a lockfile workflow that I've never seen enough value in converting over. uv is clearly much faster but that's a pretty minor consideration unless I were for some reason changing project dependencies all day long. Perhaps it never grabbed me as much because I've been running basically e…

2 things: First, you can (and should) replace your `pip install` with `uv pip install` for instant speed boost. This matters even for Docker builds.

Second, you can use uv to build and install to a separate venv in a Docker container and then, thanks to the wonders of multistage Docker builds, copy that venv to a new container and have a fully working minimal image in no time, with almost no effort.

Post reply on HN