• Czele@lemmy.world
    link
    fedilink
    arrow-up
    3
    ·
    3 days ago

    Because as the article stated they have rejected Rust back in 2024. I can remember that clearly. Back then they gave some few reasons why Rust was not a good fit, i dont remember the details but for me it made an overall impression that they dont like Rust and wont go with it ever. So what a surprise to read that huh!

    • LeFantome@programming.dev
      link
      fedilink
      arrow-up
      3
      ·
      3 days ago

      Andreas did not like the Rust community. It sounds like that is still true.

      He also thought that Rust integrates poorly into project with a deep C++ OOP hierarchy. That is probably still true as well.

      It is telling that the first project was a total rewrite of the entire JavaScript engine. There is no shared hierarchy and a well defined boundary between the C++ and Rust code. That may be a sign of things to come.

      We may see entire modules that are either all Rust or all C++ rather than more fine grained mixing.

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

        He also thought that Rust integrates poorly into project with a deep C++ OOP hierarchy. That is probably still true as well.

        Is there any language that can do that? As far as I know there isn’t. You can use SWIG or whatever but it’s just as awful as any Rust/C++ interop. There’s Carbon, but that’s a work in progress.

        IMO if you need integration with a deep C++ OOP hierarchy your options are a) give up and just use C++, or b) pain, no matter what language you target.