I recently ran into a bug in the latest version of cmake that breaks it completely in my system, can’t compile shit and it just does a coredump.
What is worse is that I can’t even report the bug because I can’t get the registration email from the cmake gitlab. I checked the manjaro repos and their cmake version is 2 versions older than the one that has the bug that left me thinking for a while lol.
sudo is bloat
Flatpak is like the most bloated thing ever because of the runtime and all the dependencies it needs.
I did a test, flatpak with just firefox installed used 3 GiB of space.
While 15 appimages that includes heavy applications like libreoffice, kdenlive and two web browsers uses 1.2GiB.
Both servers were running musl libc instead of glibc for a while. This gave me a couple of random issues, but eventually I got tired and switched back to glibc.
musl in a nutshell
since i3 dies not work on Wayland.
Might wanna drink a bit more coffee btw (sorry I couldn’t hold it lol).
MiB and MB are not the same thing. Just that many CLI tools in linux use MiB instead so I just got used to typing MiB lol.
Because it is not exactly 10MiB. Should have used about instead of like though.
https://github.com/swaywm/sway/issues/8002
https://github.com/swaywm/sway/issues/8001
https://github.com/swaywm/sway/issues/8000
Also this issue which affects xfce apps in wayland:
https://gitlab.xfce.org/xfce/thunar/-/issues/1304
I also need to find a way to do “window devour” in sway.
I also tried Hyprland and it was a total nope for me, I wasted my time reading the wiki pinning workspaces to certain monitors only for hyprland to tell me that shit was deprecated. I also found that I can’t move a floating window between displays in hyprland, as the move left/right commands move the floating window to the left or right of the display and don’t actually move it left or right, that means the window gets stuck in the left or right side of the display when trying to move it into the next.
edit: And my polybar is a long config for multiple displays as well that has several features I worked on and I really don’t wanna bother migrating to another bar:
I have indicators of cpu usage (which when click change the cpu scheduler), mem, gpu, etc, It also prints the names of the windows in the scratchpad which is the Xfce4-terminal Mate-calc in this case, the current workspace, the window class name and instance of the window with focus, the currently playing music track with playerctl, the volume in decibels, the current network speed, etc.
doas uses like 10MIB less of mem than sudo.
?
I said: “I will daily drive wayland once sway fixes their compatibility bugs with i3” That is I am not using wayland at the moment and I’m using i3 (x11) due to bugs in sway.
Sway is the wayland window manager that is a “drop in” replacement of i3. I can’t use it right now because it has several bugs that prevent me from using it.
I will daily drive wayland once sway fixes all their compatibility bugs with i3 and once polybar works on wayland as well.
In this case the issue was that a change between kde5 and kde6 let to the variable being defined as somepath / (notice the space).
It is a bug, and not only that, it is KDE6 related lmao. It’s the steam bug again!
I just use appimages, they are even smaller than native packages many times due to their compression, for example libreoffice being 300 vs 600 MiB, librewolf 110 vs 330 MiB, etc.
They are already doing that, and plenty of commits as well.
The main question now is if it will be further developed once they get the automatic builds up again. The good news is that Yuzu doesn’t need much improvement now, just a few days before the lawsuit they did some very needed vram usage fixes so now development only has to focus on getting future titles to launch.
edit: Of course I’m talking about the pc builds, Getting android to work was a nightmare even for the original devs
You don’t have steam-runtime instead of steam-native on nix?
Flatpak usually ships very outdated drivers.
I’ve been in the support channel for yuzu linux, and you would not believe all the issues people have with games freezing, etc that are instantly fixed by using the appimage instead of the flatpak.
Also flatpaks are non-xdg compliant, since it creates the useless ~/.var directory. And they have said over and over that they won’t fix that. So fuck them.
Not to mention all the issues people have with their theming and integration into the system.
Appimages are just simpler and better, the other day I was thinking how many issues would be fixed if Steam shipped as an appimage.
And depending on how you go about, appimages will even take less disk space than flatpaks or native packages even though you don’t get shared libraries with those, because they are compressed which reduces their size significantly.
Like for example the LibreWolf appimage is 110MiB while a the native package for librewolf 300MiB. Same with LibreOffice, the appimage is 300MiB while the native package is 600 MiB.
It also makes it easier to downgrade if you run into an issue, like I had to had an older appimage of ferdium because the latest version is affected by an electron bug that broke its zoom functionality.
Flatpak itself violates the xdg base dir spec by making ~/.var
I didn’t know flatpak was using MB instead of MiB, ever since I moved to linux most apps I’ve used report MiB instead.
Edit: I checked my CLI tools because the guy said that CLI tools are all over the place, the only one that doesn’t use MiB is lf.
Edit2: I lost my shit when I checked the profile of patrick and the first thing in the description says gnome developer, holy shit this can’t be lmao.
They are also shipping x86-64 v3 packages. Something that on arch you still rely on 3rd party repos.