• Ephera@lemmy.ml
    link
    fedilink
    English
    arrow-up
    1
    ·
    2 days ago

    I mean, it sounds like it’s gonna be a fairly large codebase. Rust is definitely better equipped for large codebases than Python…

    I do agree that Python could give them more outside contributors, but from my experience, I don’t think it’s worth swaying from your preferred tooling for that. Outside contributions will make up barely a fraction of code changes either way, so you should rather ensure that your core team is productive.

    • TehPers@beehaw.org
      link
      fedilink
      English
      arrow-up
      2
      ·
      1 day ago

      Python can also be used for large codebases (thanks uv), but I agree that Rust is better suited to the job.

      • Ephera@lemmy.ml
        link
        fedilink
        English
        arrow-up
        1
        ·
        1 day ago

        Are you referring to the workspace feature of uv? Is that working well?

        Management might want us to revive a project from a few years ago, which is like 5% Python, but for which we had to build a homegrown horrid implementation of workspace builds, using shell scripts and symlinks. We’d definitely want to get rid of that, if uv’s workspace builds work at all, really. 🫠

        • TehPers@beehaw.org
          link
          fedilink
          English
          arrow-up
          2
          ·
          1 day ago

          uv’s workspaces work, yep. It’s honestly great. Haven’t really run into any issues with them yet.