she/her

  • 0 Posts
  • 88 Comments
Joined 2 years ago
cake
Cake day: August 3rd, 2023

help-circle








  • It’s about the certainty to have what you want, where you want it, reliably. I run NixOS with Impermanence, which means I reset my root partion on every boot, and have what state I need specifically opt-in. And I run a shared config over multiple devices (home PC and Laptop), so installing something on one also installs it on the other, next time I rebuild. It certainly takes time getting used to, but I’ve been really enjoying it so far











  • It’s fair to want to learn (and it’s certainly a good skill to have), but the question is what you’d rather see in a large, production environment. Guard rails are usually there for a reason. As for the control: you actually can program memory-unsafe (and in kernel development you often have to!) in Rust. The difference is that in Rust it’s explicitly marked by an unsafe block:

    unsafe {
      ...
    }
    

    That way you get the same, fine-grained control over low-level processes, but someone else reading your code can at a glace spot where potential memory bugs may be.

    In the end, languages are a tool. Especially for personal projects, everyone should just go with what’s fun to them. I personally think it makes sense, logistically, to slowly transition legacy C-based projects to Rust, because it makes onboarding new developers easier, while keeping the same memory safety that requires years of experience otherwise, basically for free. But there’s really no rush to rewrite anything that’s working well in Rust