you are viewing a single comment's thread
view the rest of the comments
[–] 22 points 2 days ago (8 children)

Perhaps it’s vibecoded slop?

  • source
  • parent
  • hideshow 8 child comments
  • [–] 11 points 2 days ago (5 children)

    Rust apps seem to always be on the heavy side, maybe depends how much debug info they leave in

  • source
  • parent
  • hideshow 5 child comments
  • [–] 36 points 2 days ago (1 child)

    Indeed, they’re probably shipping a backtrace symboliser, and since there’s no system-wide equivalent of libc to link against, they’ll be including the entire Rust standard library with the binary too.

    My other hunch is the Krisp noise cancellation ML model is a huge chunk of the memory footprint.

  • source
  • parent
  • hideshow 1 child comment
  • [–] 7 points 1 day ago (2 children)

    I once played around with reverse engineering a Rust program. I compiled the optimized version of the standard "hello world" program which somehow turned into 50,000 lines of assembly.

    It looked like it copied over dozens of functions from libc and the data section was filled with every single possible error string "file not found", "connection timed out", etc. as if there was a possibility of hello world generating an access denied error.

  • source
  • parent
  • hideshow 2 child comments
  • [–] 2 points 1 day ago

    Rust has static linking, you get the necessary (and some unnecessary) parts of the standard library in your binary instead of the user having to install the library the way you have to have a libc installed. Makes for fatter binaries but much easier compatibility.

  • source
  • parent