• 0 Posts
  • 65 Comments
Joined 2 years ago
cake
Cake day: November 28th, 2022

help-circle
    1. Get kicked from freedesktop for fostering a toxic community.
    2. Ditch wlroots for your own compositor.
    3. Shit on other compositors in your spare time.
    4. Tell people they should just be plugging into Hyprland instead of rolling their own compositor.

    Man if I was concerned about sinking the time to make a configuration for the compositor with a bus factor of 1 man-child, and a toxic community; I can’t imagine anybody investing the time to make a compositor is going to want to hitch themselves to that cart.

    The compositor is really solid and makes for a great user experience but I’ll be fucked if every word vaxry writes doesn’t make me want to move to sway or niri.


  • Nixpkgs has more and newer packages than the aur.

    The initial time to get shit done is longer; you can’t simply make install, but honestly you shouldn’t have been doing so on arch anyway.

    Making your own derivation is much easier than making your own PKGBUILD and should be considered in those terms because you’re not just shoving some binary into /usr/bin for it to explode later when glibc updates.

    When things fuck up, reverting to your previous config is at worst a reboot away.

    I have much less time than I used to, so moving from arch to Nixos has prevented the time otherwise wasted in an arch-chroot trying to fix issues like the kernel upgrading past what the zfs-dkms supports.

    If you’re using specialised proprietary tools, working them in with Nix can be an absolute nightmare, but I use a debian container for them.





  • I work with SoC suppliers, including Qualcomm and can confirm; you need to sign an NDA to get a highly patched old orphaned kernel, often with drivers that are provided only as precompiled binaries, preventing you updating the kernel yourself.

    If you want that source code, you need to also pay a lot of money yearly to be a Qualcomm partner and even then you still might not have access to the sources for all the binaries you use. Even when you do get the sources, don’t expect them to be updated for new kernel compatibility; you’ve gotta do that yourself.

    Many other manufacturers do this as well, but few are as bad. The environment is getting better, but it seems to be a feature that many large manufacturers feel they can live without.



  • If you’re messing with ACLs I’m not sure deduplication will help you much; I believe (not much experience with reflinks) the dedup checksum will include the metadata, so changing ACLs might ruin any benefit. Even if you don’t change the ACLs, as soon as somebody updates a game, it’s checksum will change and won’t converge back when everyone else updates.

    Even hardlinks preserve the ACL… Maybe symlinks to the folder containing the game’s data, then the symlinks could have different ACLs?









  • apt_install_coffee@lemmy.mltoProgrammer Humor@programming.devIs this a Nut?
    link
    fedilink
    arrow-up
    1
    arrow-down
    1
    ·
    edit-2
    8 months ago

    No, I’m saying that when people run into strange bugs, sometimes they put together an issue (like the person behind cve-rs), and sometimes they quietly work around it because they’re busy.

    Seeing as I don’t often trawl through issues on the language git, neither really involve notifying me specifically.

    My lack of an anecdote does not equate to anecdotal evidence of no issue, just that I haven’t met every rust developer.


  • Yes, the problems rust is solving are already solved under different constraints. This is not a spicy take.

    The world isn’t clamoring to turn a go app into rust specifically for the memory safety they both enjoy.

    Systems applications are still almost exclusively written in C & C++, and they absolutely do run into memory bugs. All the time. I work with C almost exclusively for my day job (with shell and rust interspersed), and while tried and tested C programs have far fewer memory bugs than when they were first made, that means the bugs you do find are by their nature more painful to diagnose. Eliminating a whole class of problems in-language is absolutely worth the hype.



  • The code used in cve-rs is not that complicated, and it’s not out of the realm of possibility that somebody would use lifetimes like this if they had just enough knowledge to be dangerous.

    I’m as much a rust evangelist as the next guy, but part of having excellent guard rails is loudly pointing out subtle breakages that can cause hard to diagnose issues.