Alt account of @Badabinski

Just a sweaty nerd interested in software, home automation, emotional issues, and polite discourse about all of the above.

  • 0 Posts
  • 17 Comments
Joined 3 months ago
cake
Cake day: June 9th, 2024

help-circle



  • Nah, the slow hop-hop-hop is like a jog. Mustelids can fucking zoom if they’re in danger or after prey. Like, even dopey-ass domesticated ferrets can get going pretty damn quick when they’ve been hurt or feel threatened. Nobody has posted what species of otter attacked this lady, but river otters can reach speeds of 47 kph (29 mph) on land. Sea otters are slow and fat, but these weren’t sea otters.

    You aren’t outrunning a pack of otters in a sprint. It’s no question that you could outrun them over a long distance, but mustelids are zoomy little fuckers.

    (note that I like mustelids and had 4 ferrets, so please don’t mistake my tone as being sour on them)

    EDIT: holy shit, ferrets can be bred and trained to run at like 22 mph. That’s insane!



  • Badabinski@kbin.earthtoLinux@lemmy.mlGoldilocks distro?
    link
    fedilink
    arrow-up
    25
    arrow-down
    8
    ·
    6 days ago

    For me, it’s Arch for desktop usage. When I first started using Arch it would not have been Arch, but now it’s Arch. The package manager has great ergonomics (not great discoverability, but great ergonomics), it’s always up to date, I can get a system from USB to sway in ~20 minutes (probably be faster if I used the installer), it’s fast because it doesn’t enable many things by default, and it’s honestly been the most reliable distro I’ve ever used. I used to use OpenSUSE ~10 years ago, and that broke more in one year than Arch has in ten.

    I personally feel like Arch’s unreliable nature has been overstated. Arch will give you the rope to hang yourself if you ask for it, but if you just read the emails (or use a helper that displays breaking changes when updating like paru) and merge your pacnews then you’ll likely have a rock solid system.

    Again, this is all just my opinion. It’s easy for me to overlook or forget all of the pain and suffering I likely went through when learning how to Arch. I won’t recommend it to you, but I’ll happily say how much I’ve come to enjoy using it.


  • Jesus wept. I’ve always had a morbid fascination with weapons and this one definitely “satisfies” the morbid part. I agree with the other person. This is better than cluster munitions since it will result in far fewer civilian casualties, but it’s also tremendously fucked. It makes me feel about as icky as thermobaric bombs do.

    I hate to think what the improvement to this idea will look like. I’m sure it will be improved upon, since Northrop now has plenty of field data showing the effectiveness of this design.


  • The tiered storage stuff is pretty cool. You can say “I want this data on this disk, so if I get a cache miss from a faster disk/RAM it’ll come from this other disk first.”

    I believe it also has some interesting ways of handling redundancy like erasure coding, and I thiiiink it does some kind of byte-level deduplication? I don’t know if that’s implemented or is even still planned, but I remember being quite excited for it. It was supposed to be dedupe without all of the hideous drawbacks that things like ZFS dedupe have.

    EDIT: deduplication is absolutely not a thing yet. I don’t know if it’s still on the roadmap.

    EDIT: Erasure coding is deffo implemented, however.


  • Badabinski@kbin.earthtoLinux@lemmy.mlHyprland is now fully independent!
    link
    fedilink
    arrow-up
    62
    arrow-down
    4
    ·
    edit-2
    2 months ago

    What if you need to file a bug? What if you have a question on the config that’s not easily answered by the docs? If you never, ever find bugs and never, ever have questions, then sure, separate the two. There are genuinely people like that, but they’re not common. If you’re one of them, then I’m genuinely glad for you.

    My opinion is this: You use software. You don’t use people, but you sure as hell rely on them.





  • The other person may have responded with a fair amount of hostility, but they’re absolutely correct. I run Kubernetes clusters hosting millions of containers across hundreds of thousands of VMs at my job, and OOMKills are just a fact of life. Apps will leak memory, and you’re powerless to fix it unless you’re willing to debug the app and fix the leak. It’s better for the container to run out of memory and trigger a cgroup-scoped OOM kill. A system-wide OOM kill will murder the things you love, shit in your hat, and lick your face like David Tennant licked Krysten Ritter.