• FizzyOrange@programming.dev
    link
    fedilink
    arrow-up
    2
    arrow-down
    2
    ·
    5 days ago

    Why bother with the significant pain of FFI when you can just write the whole thing in Rust?

    Also “the critical parts” is mostly a myth. After a small amount of optimisation, the vast majority of programs do not have nice isolated hotspots.

      • FizzyOrange@programming.dev
        link
        fedilink
        arrow-up
        1
        arrow-down
        2
        ·
        5 days ago

        Rust has scripting support. It’s nightly only but that’s not actually a big deal since running nightly is trivial.

        It has some limitations currently, but… so does Python.

        • lime!@feddit.nu
          link
          fedilink
          arrow-up
          2
          arrow-down
          1
          ·
          5 days ago

          it’s just such an odd question. you know nothing about my domain or my requirements, you just assume i can or want to use rust.

          • FizzyOrange@programming.dev
            link
            fedilink
            arrow-up
            1
            arrow-down
            2
            ·
            4 days ago

            Rust is pretty great in almost all domains. The only ones where I think Python is a sensible choice are research, where a REPL is really useful (think Jupyter).

            • lime!@feddit.nu
              link
              fedilink
              arrow-up
              1
              arrow-down
              1
              ·
              4 days ago

              the stdlib of rust is woefully lacking, proper error handling is way too verbose, the dependency chains are massive and unauditable, and all the implicitness makes it hard to reason about stuff like a.from() without proper editor support which makes code review a nightmare. i do like ccontract-driven design though. all in all i think i’ll stick to zig if i need safety.