• 0 Posts
  • 60 Comments
Joined 6 years ago
cake
Cake day: May 31st, 2020

help-circle







  • Yeah, it’s qualities that are useful for humans, too, like frontloading all the errors to compile time + good compiler error messages.

    Like, I’m annoyed that people will be irrational about it, much like they associate Rust with rewrites in permissive licenses, even though it is just a tool. It entirely depends on how you use the tool.
    But irrational people gonna irrational. Not much you can do about that…









  • Ephera@lemmy.mltoTechnology@lemmy.ml•LLM Voice
    link
    fedilink
    arrow-up
    5
    ·
    18 days ago

    Worst part is, at some point in my life, I believed there to be a correlation between words read and information acquired. I do not believe that anymore. You give that LLM three points to cover and the instruction to fill a whole page, of course it’s going to pad with as much dead air as possible.


  • Because they take away tons of libraries I normally use.
    For example, for querying low-level system information (like I imagine you need to do a lot in systemd), I’d normally use the nix library. If I can’t do that, I have to use libc directly. Well, and write a wrapper for it, if they don’t already have one.

    So, I don’t want to say it would be extremely hard, but it would still mean learning a different way of doing things…


  • Yeah, in detail, they use or can use:

    • Syntax + tooling for it, like editors, linters, formatters
    • Compiler (rustc, which enforces memory+thread-safety for the parts not implemented in C)

    They’ve replaced:

    • std library → core library + their own implementation of types that do memory allocations, so in particular dynamically-sized types like lists and strings
    • Cargo → their own Meson definitions

    What they don’t use:

    • the library ecosystem of Rust (although apparently they’ve got own implementations of “logging, command-line argument handling, event processing, and error management”)

    It does sound like someone thought about this stuff, but yeah, as a Rust dev, it also sounds like I would struggle…


  • Fair enough, I guess.
    Personally, I don’t really see the point, because there’s hardly any projects that can be compiled with just rustc.

    I mean, cargo is actually surprisingly useful for normal users, because there’s a decent chance you can compile medium-sized Rust projects without having to jump through endless hoops.

    But yeah, at that point, you’re adding a nontrivial number of megabytes to user installations for something they might not use. I would guess that even just rustc is larger than gcc and clang, since it implements more sophisticated logic…