Comment on Rust is Eating JavaScript

• Dark_Arc@social.packetloss.gg ⁨2⁩ ⁨months⁩ ago

  1. It’s statically compiled and isn’t dependent on system binaries and won’t break if there if the system has the wrong version like C/C++, allowing you to distribute it as a single binary without any other installation steps

  You can do that with C++ too.

  2. Still produces fairly small binaries unlike languages like Java or C# (because of the VM)

  I mean, the jars are actually pretty small; but also I really don’t get the storage argument. I mean we live in a world where people happily download a 600 MB discord client.

  3. Is a modern language with a good build system (It’s like night and day compared to CMake)

  Meson exists … as do others.

  4. And I just like how the language works (errors as values etc.)

  Fair enough; though why? What’s wrong with exceptions?

  I work in a code base where I can’t use exceptions because certain customers can’t use exceptions, and I regularly wish I could because errors as values is so tedious.

  source

  • Zykino@programming.dev ⁨2⁩ ⁨months⁩ ago

    3. Is a modern language with a good build system (It’s like night and day compared to CMake)

    Meson exists … as do others.

    But they are not the default option. And your new job may not use them.

    4. And I just like how the language works (errors as values etc.)

    Fair enough; though why? What’s wrong with exceptions?

    Exceptions is a non standard exit point. And by “non standard” I’m not talking about the language but about its surprise appearance not specified in the prototype. Calling double foo(); you don’t know if you should try/catch it, against which exceptions, is it an internal function that may throw 10 level deep ?

    By contrast fn foo() -> Result<f64, Error> in rRst tell you the function may fail. You can inspect the error type if you want to handle it. But the true power of Result in Rust (and Option) is that you have a lot of ergonomic ways to handle the bad case and you are forced to plan for it so you cannot use a bad value thinking it’s good:

    • foo().unwrap() panic in case of error (see also expect)
    • foo().unwrap_or_default() to ignore the error and continue the happy path with 0.0
    • foo().unwrap_or(13.37) to use your default
    • foo()? to return with the error and let the parent handle it, maybe

    source

    • tzrlk@lemmy.world ⁨2⁩ ⁨months⁩ ago

      That sounds a lot like how checked exceptions work, though with some terser handling syntax.

      source

      • Zykino@programming.dev ⁨2⁩ ⁨months⁩ ago

        First time I hear about checked exceptions. How do you use them ? Are you forced to handle them explicitly ? Is the handling checked at compile time ?

        source

        • -> View More Comments
    • Dark_Arc@social.packetloss.gg ⁨2⁩ ⁨months⁩ ago

      But they are not the default option. And your new job may not use them.

      Who cares if it’s the default? If it’s the best tool, use it.

      It’s to have a reason for “going Rust” be the build system, especially in the context of something as new as a WASM context where basically any project is going to be green field or green field adjacent.

      Exceptions is a non standard exit point. And by “non standard” I’m not talking about the language but about its surprise appearance not specified in the prototype. Calling double foo(); you don’t know if you should try/catch it, against which exceptions, is it an internal function that may throw 10 level deep ?

      And that’s a feature not a bug; it gets incredibly tedious to unwrap or forward manually at every level.

      By contrast fn foo() -> Result<f64, Error> in rRst tell you the function may fail. You can inspect the error type if you want to handle it. But the true power of Result in Rust (and Option) is that you have a lot of ergonomic ways to handle the bad case and you are forced to plan for it so you cannot use a bad value thinking it’s good:

      You can do this in C++ en.cppreference.com/w/cpp/utility/expected (and as I said, if you feel so inclined, turn off exceptions entirely); it’s just not the “usual” way of doing things.

      source