Expert developer, Buddhist

  • 0 Posts
  • 61 Comments
Joined 1 year ago
cake
Cake day: June 21st, 2023

help-circle





  • Lung@lemmy.worldtoLinux@lemmy.ml“Systemd is the future”
    link
    fedilink
    arrow-up
    12
    arrow-down
    2
    ·
    13 days ago

    I guess reading the history, systemd did a better job of dependency resolution and parallel loading of startup services. Then some less interesting stuff like logins, permissions, and device management - which definitely seems out of scope. There’s been like 15 alternatives since it was made, but none of them got critical mass, and now pretty much every mainstream distro can’t run without it. Sad face

    While I’m here complaining, I really miss the days when Arch was configured from a single global file that handled many things like setting your hostname, locale, etc. I think it was dropped bc of maintenance & being not unixy enough. Kinda ironic


  • Lung@lemmy.worldtoLinux@lemmy.ml“Systemd is the future”
    link
    fedilink
    arrow-up
    69
    arrow-down
    1
    ·
    edit-2
    13 days ago

    I mean that argument is ridiculous, saying that things are “documented” when the thing is literally called tmpfiles.d and the man page starts with the following explanation:

    It is mostly commonly used for volatile and temporary files and directories (such as those located under /run/, /tmp/, /var/tmp/, the API file systems such as /sys/ or /proc/, as well as some other directories below /var/).

    So basically some genius decided that its a good idea to reuse this system for creating non-tmp directories. Overall my opinion of systemd is reluctant acceptance though I always wondered why the old way was a problem. Need a service started on boot? Well, we had crontab and sysvinit with some plain files. Need a service shut down? Well that’s the kill command. I guess I don’t really know why systemd was made












  • Well, generously I think this guys point is that you shouldn’t use rust for developing actual game logic (you’d use those higher level scripts). For game logic, it’s bad bc it’s not very iterative - and the rest of the stack sucks too but everyone knew that getting into it. But yes, I’m sure you could make a game engine with it


  • Yeah idk Rust seems superior in the less useful ways. Go’s tooling, fast build times, hyper efficient parallel GC (not kidding, it’s world class), interfaces, and simplicity are really killer features. Though honestly, even after many years, channels still confuse me - it’s like plumbing, but plumbing needs pressure gauges, emergency valves, and buffers - so it always ends up with this string cheese of events spread over multiple files. I end up using a mutex half the time


  • Lung@lemmy.worldtoRust@programming.devLeaving Rust gamedev after 3 years
    link
    fedilink
    arrow-up
    29
    arrow-down
    6
    ·
    edit-2
    2 months ago

    Interesting to read about how borrow checker constraints affect iteration speed in game dev

    Yeah seems like the wrong choice overall. I think Rust found its way to the niche of being a “new C” that’s pretty much just for when you need something very optimized like kernel modules and backend hotpaths (and Firefox I guess). That’s a cool niche to fill

    I most enjoy Go for servers, and JS unfortunately is mandatory for many things. I don’t tend to write code that requires Rust’s performance. For mobile, the Flutter stack with Dart is pretty cool. For automation & simple cli, shell scripts suit me fine (but any language can do this ok). Python is tragic, Java is evil, C# is MS Java, node/npm are a toxic hazard, and webassembly with preloaded runtimes in browsers cant come soon enough