ShittyKopper [they/them]

I’m boring and I shitpost and tech-post all over the place. Big fan of Ea-nāṣir.

Microblogs: @[email protected]

  • 2 Posts
  • 25 Comments
Joined 1 year ago
cake
Cake day: June 22nd, 2023

help-circle


  • I started dual booting Linux back when Steam for Linux was reasonably new and Portal 2’s native port was on beta. Briefly went back to Windows after building a new, much powerful system for about a year, DXVK & later on Proton happened, and now all the games I care about work flawlessly.

    There have been games on my Steam library that I never ran on Windows despite them not officially supporting Linux.

    With the deck I seriously hope devs slowly but surely start thinking about native ports as well, but I won’t mind waiting another - uhh, 10?! - years for that to happen. I expect Steam Linux Runtime & Flatpak to be the DXVK & Proton of native ports - as in, the thing that will make them “viable” instead of “theoretically possible”. Win32 is still the most stable ABI on Linux after all.





  • Rootful Podman & podman-compose. Waiting on the version of Podman that supports passt to hit Debian Bookworm or backports to attempt rootless. Deployed with Ansible except a few manual parts like creating the Postgres databases themselves.

    No auto updates or notifications so far, as there seems to be a couple incompatibility issues left with Watchtower & Podman. Although since I switched CrowdSec to monitor journald instead of the Podman socket I don’t really have a reason to keep the daemon running, and I think that’s for the best.



  • Wayland very good on AMD and Intel these days. Nvidia was unsupported, but last year nVidia made a business decision to support EGL(?) so with fresh drives work has begun in Gnome and KDE to support Nvidia in Wayland. I’m not sure how mature Nvidia on Wayland is yet

    Clarification: GBM is what Intel, AMD and the general “nice players” of the Linux graphics ecosystem decided, whereas EGLStreams was something NVidia came up with because it worked better with their proprietary drivers (AFAIK)

    Gnome and KDE were fine going out of their way to support both, but smaller implementations such as wlroots (the thing behind sway and Hyprland and other non-Weston “window managers”) didn’t feel the tradeoff was worth it (in both philosophical and manpower reasons) and stuck to GBM.

    NVidia comparatively recently “caved in” and got GBM support working (alongside kernel mode setting & other terms you don’t really need to know about), and being one of the few proprietary players in the ecosystem they have not been able to benefit from help from the community, which is one of the reasons why their Wayland support is immature compared to the likes of Intel and AMD.






  • GNOME’s stance on user customization has been “users can do whatever they feel like using 3rd party tools like Gradience or entirely custom CSS, but if you’re a distro maker then only use the Approved Ways™ to customize things”

    Now, I have zero clue if that solves anything (it very likely doesn’t), but it’s actually more than most people give them credit for.

    I’d say “go join in on the issue tracker and tell GNOME about this” but hearing from some people who tried that before you I’m not too hopeful that would do much of a difference. All I know is that complaining here isn’t going to solve anything.



  • The thing about NixOS is that while using packages are easy, creating them are still really hard and/or undocumented.

    With most popular services already being packaged by people who know what they’re doing this isn’t that big of a deal, but when I want to try out something from Joe Schmoe’s GitHub (or worse, something I made myself) it is much easier for me to throw together a “good enough” Dockerfile and compose.yml together in barely a hour of work than to dig into Nixpkgs internals and wrestle with Nix’s syntax.







  • Definitely not Gentoo based, but if you can get by with their unique approach to basically everything, NixOS can be pretty interesting, in that while it is technically source based, binary caches are widely used to basically “pretend” to be a binary distro. And it does let you patch things shouid you want it (at the expense of recompiling everything that even slightly comes in contact with the patched package)

    There are some parts that are too “baked in” to change – requiring systemd, for instance – so that may be a dealbreaker for you.