Astral to join OpenAI
astral.sh
Astral has entered into an agreement to join OpenAI as part of the Codex team.

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.

    • siera@jlai.luEnglish
      0·
      2 months ago

      The developers were already genAI users.

      But now I fear that the tutorial will include an “openai init”, and other non-deterministic subscription-based commands for ruff and uv and that will be what is pushed.

  • prism@lemmy.dbzer0.comEnglish
    0·
    2 months ago

    Sigh. I knew uv and ruff were too good to be true. Just hope the community can fork before it all goes to crap.

  • Satomune@lemmy.worldEnglish
    0·
    2 months ago

    Hi, I’m an AI engineer based in Japan, and I’m expanding into the U.S. market to work with more long-term clients. I’m looking for an American collaborator who can act as a communication bridge between me and U.S. clients.

    I will handle the technical side myself, including project planning, AI development, and software implementation. Your role would be to join meetings, help with smooth communication, and support the client relationship side.

    If this sounds like a good fit, please send me a message.

  • TheAgeOfSuperboredom@lemmy.caEnglish
    0·
    2 months ago

    I find that Python requires a fair bit of discipline to keep it readable, and I’ve seen some very unreadable code written by people. Vibe coding with Python’s dynamic nature seems like a match made in hell.

    • Eager Eagle@lemmy.worldEnglish
      0·
      2 months ago

      It’s manageable if you pass along these rules to the LLM. I’ve actually had more success asking the LLM than giving code reviews to some interns, and even someone who coded professionally before.

      • badgermurphy@lemmy.worldEnglish
        0·
        2 months ago

        Right, but aren’t the interns in training specifically to get better at that than they are today, and eventually surpass the abilities of the AI?

        These LLMs are at best OK at this stuff, and are not improving at any sort of convincing rate. If you don’t train anyone to be better than the LLM, the retirement of your generation will make the whole industry you’re in at best, OK at its job.

        • Eager Eagle@lemmy.worldEnglish
          0·
          2 months ago

          Ok, I’m not suggesting replacing humans with AI and I despise companies trying to do this unsustainable practice.

          With that out of the way, I’ll restate that LLMs follow some rules more reliably than humans today. It’s also easier to give feedback when you don’t have to worry about coming across as a pedantic prick for pointing out the smaller things.

          On your point that LLMs are not improving; well, agents and tooling are definitely improving. 6 months ago I would need to babysit an agent to implement a moderately complex feature that touches a handful of files. Nowadays, not as much. It might get some things wrong, but usually because it lacks context rather than ability. They can write tests, run them, and iterate until it passes, then I can just look at the diff to make sure the tests and solution makes sense. Again, something that would fail to yield decent results just in the last year.

    • galaxy_nova@lemmy.worldOPEnglish
      0·
      2 months ago

      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

      • TheAgeOfSuperboredom@lemmy.caEnglish
        0·
        2 months ago

        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.

  • Axum@lemmy.blahaj.zoneEnglish
    0·
    2 months ago

    If all this does is fund astral and by extension uv I don’t see a problem here.

    Hell, I’d take ai Corp money to fund making good tools for the community, as it’s one less stack of cash being used on bullshit datacenters.