• atzanteol@sh.itjust.worksEnglish
      14·
      3 months ago

      It forces you to be careful in the way it wants you to be careful. Which is fine, but it makes it a strange beastie for anyone not used to it.

          • Kairos@lemmy.today
            6·
            3 months ago

            I feel like a garbage collector would be too much a performance hit for kernel stuff.

            • InverseParallax@lemmy.worldEnglish
              3·
              3 months ago

              2 things:

              1. It’s more the determinacy, a GC randomly fires up and your systems stops for some long amount of time. There are pauseless GCs but that’s a different nightmare.

              2. The kernel has things similar to GCs. They’re used for more specialized tasks, and some (like rcu) are absolute nightmares that have take decades to get working.

    • Fonzie!@ttrpg.network
      92·
      3 months ago

      And because it looks like C, JavaScript, Bash and a few others all mixed up together.

      I’ve heard Rust described as “Rust is what you get when you put all the good features of other programming languages together. You can’t read it, but it’s freaking fast!”

    • nous@programming.devEnglish
      7·
      3 months ago

      C is easier to get a program to compile. Rust is easier to get a program working correctly.

    • PushButton@lemmy.world
      74·
      3 months ago

      it’s more “it forces you to make it burrow checker friendly”.

      A burrow checker is not the only mechanism to write safe code. All the mess of Rust is all because this is the strategy they adopted.

      And this strategy, like everything in this world, has trade offs. It just happens that there are a lot, like, - a lot -, of trade offs, and those are insufferable when it comes to Rust…