• 0 Posts
  • 137 Comments
Joined 3 years ago
cake
Cake day: June 6th, 2023

help-circle


  • Staying compatible with LTS releases should absolutely be the goal, but that takes work from both sides.

    If Debian is applying backported patches to old software (I think the oldest version I saw was 6 years out of support) that generates a nightmare to support for package maintainers. If there are features which are not supported since the version is so old, but there are backported security patches which change the API, the developers would essentially have to maintain a specific version for each LTS distro’s specific set of patches, and the number of versions you have to maintain and the length of time you need to maintain them for quickly becomes impossible to manage.

    Stable is nice, but you can have stability without being criminally outdated, as Trixie shows. The ideal is to have a stable and up to date distribution.

    And yes, most users would be fine due to just being in the browser, but thats true of literally any OS or distro, not specific to this.



  • Debian is nice & boring, but I have had issues with how old its kernel and software versions are. 6.12 isn’t too bad for Trixie, but previously it was really terrible. When I was running Bookworm, I ran into plenty of situations where software I was compiling or getting from outside the repos (for niche software), wasn’t backwards compatible to the library versions Debian provided.

    No hate for Debian, but it just doesn’t work for a lot of people. However, these days I would go for Debian over Ubuntu 10 times out of 10.



  • If you just want portability, then this could be useful. However, in my opinion a large part of why I use a shell script is to avoid compilation and just hack something together. If your goal is shell scripts that are easier to write you could also check out other shells:

    • fish is the easiest to use in my opinion, but is not POSIX compliant so you do have to learn the syntax.
    • zsh is a nice quality-of-life upgrade over BASH, tweaking the little things
    • There are also things like xonsh which use Python syntax for shell scripting, but I dont have personal experience with them.


  • Vanilla KDE on desktop, Niri WM+Noctalia shell on laptop. Firstly, because for some reason I cannot get any touchpad gestures to work on KDE, and secondly because the niri paradigm of horizontal tiling is just perfect for a laptop. I tried to use Gnome for a while before landing on Niri, but the lack of configurability and the reliance on extensions for basic functionality drove me nuts.









  • You can’t run steam with no compositor whatsoever, but you can use the steam deck’s solution of using their gamescope micro compositor for everything. You should be able to install gamescope and just run gamescope -e {other CLI options} steam (assuming you’re using the native Arch package and not the flatpak).

    My experience using gamescope for steam has been very mixed, but I’ve seen a tutorial somewhere on doing exactly this.

    Gamescope isn’t necessarily the best option for every game, and having a normal compositor (which, for now, must support XWayland) is just a much more flexible solution.

    This may also be possible with something more general like xwayland-satellite, but frankly steam and all its games still run on the X11 protocol, so if you really don’t need a GUI you might be able to install a vanilla X11 instance and hook to that directly. I can’t speak to either of those options directly.

    But is this worth it, in a practical sense? No. You have a reasonably powerful system, and the only performance you’d be saving is a few percent of a single core on the CPU, which in your config is absolutely not worth it.