Today, AI is rapidly changing the way we build software, and the pace of that change is only accelerating. If our goal is to make programming more productive, then building at the frontier of AI and software feels like the highest-leverage thing we can do.
It is increasingly clear to me that Codex is that frontier. And by bringing Astral’s tooling and expertise to OpenAI, we’re putting ourselves in a position to push it forward. After joining the Codex team, we’ll continue building our open source tools, explore ways they can work more seamlessly with Codex, and expand our reach to think more broadly about the future of software development.
This is true although that’s what enforcing strict type checking and good linting is supposed to help with. I think it’s partially an issue that you can kinda just type what you think and not everyone thinks efficiently/ programmer-y
Edited for clarity
Agreed! I think both linting and type checking are extremely important to Python, but it’s also an extra step that far too many people just don’t take. And honestly, I used to get tripped up sometimes with setting up Python tooling before I started using uv.
Unfortunately I also have to work with the occasional Python script that someone just slapped together, and that’s something far too easy to do in Python. It does kind of remind me of vibe coding. Initial velocity seems high, but if you’re not thinking about it, long term maintenance tanks.
That’s not to say Python is bad, and there is certainly a lot of good Python code out there too. But it’s a language that does make it easy to make a mess, which will probably be compounded by LLMs.