I joined Lemmy back in 2020 and have been using it as qaz@lemmy.ml until somewhere in 2023 when I switched to lemmy.world. I’m interested in systemd/Linux, FOSS, and Selfhosting.

  • 131 Posts
  • 845 Comments
Joined 2 years ago
cake
Cake day: June 10th, 2023

help-circle












  • qaz@lemmy.worldtoMicroblog Memes@lemmy.worldoddly specific
    link
    fedilink
    English
    arrow-up
    7
    ·
    edit-2
    6 days ago

    When the program is running it’s probably stored with 32 or 64 bits, but that probably isn’t the case for the network packet layout. I can imagine them wanting to optimize network traffic with over 3 billion users even if it’s just a small improvement.

    Also TIL that Erlang’s VM apparently stores strings as linked lists of chars. Very strange.

    data representation of string 'phi'



  • …definitely takes some getting used to when you come from a non-memory safe language…

    I actually think it’s more like the opposite. The compiler takes the normal rules you apply to avoid issues with a non-memory safe language like C/C++ and enforces them explicitly where memory safe languages don’t have those rules at all. I think lifetimes are much more confusing if you’ve never dealt with a user after free and usually let GC deal with it.

    Also yes the compiler warnings and errors are amazing, the difference between rustc and gcc is night and day.