You die twice. One time when you stop breathing, and a second time, a bit later on, when somebody damns your soul for the last time.

  • Hafez Al-Assad
  • 0 Posts
  • 5 Comments
Joined 2 years ago
cake
Cake day: December 17th, 2024

help-circle

  • No? It wasn’t? “The OS for your e-waste” isn’t a good name for an OS this good. Also the old name was long, and with Google riling up FOSS advocates and annoying a good portion of normal users with their recent decisions, this is the perfect wave of criticism of Android and endorsement of alternatives to ride with some marketing.

    I’d say the logo needs a redesign too.

    edit: after reading the article, I think “Nurag” or “Nuragh” would’ve been better, but anything is better than the old name IMO.


  • Very integral. When someone says they’re “struggling with Rust”, it’s thanks to the borrow checker.

    Rust’s whole shtick is the way it manages memory, which is the rules enforced by the borrow checker.

    Basically:

    When you want to store values in variables in any programming language, the memory should be allocated when you need it and freed as soon as you don’t anymore.

    Traditionally there are two ways this is done:

    1. You manage it completely yourself, which is “unsafe” as you can forget to free memory you no longer need. This is called leaking memory. Or “reference” the location of something you freed previously, thereby attempting to read data you may not have permission to read (the OS will usually prevent that and kill the program), or reading and using a value you didn’t expect, causing undefined behavior and fun to deal with bugs.

    2. The language, sometimes using a process which runs alongside your main program, manages memory. Which adds lots of overhead.

    Rust has it’s own way of doing this: It adds some rules on how you can pass around references and ownership and these rules are affected by whether you can or can’t edit the referenced data. All just so the compiler knows the lifetime of the vars that hold that data and when it can free it (before the program is even compiled, so no overhead when the program is running). Not following the strict rules prevents your program from being compiled into an executable.

    The compiler gives very helpful info, tips, and pointers™ though, Rust is also know for this.


  • Oh, thanks. The site is back online.

    This is good news, but the title makes it seem a lot more interesting than it is. Everyone here already uses VPNs for everything, 'cause it’s all banned.

    This is weird though, because other distros like Arch, Debian, and their derivatives (even corporate ones (e.g. Manjaro)) were working fine. Even Flathub didn’t require a VPN. isn’t that hosted by Red Hat too?