Introducing openSUSA
Shameless flex
Yes, I spent a while reading the documentation on how to pin workspaces to certain monitors only for hyprland to tell me that it is deprecated.
Also an issue I noticed is that you can't move floating windows between displays with the move left/right commands, move left/right moves the floating window to the left or right of the display and no more, meaning that the window gets stuck at the border of the display and doesn't move more.
Also I couldn't figure out how to make hyperland run several commands in a row with one keybind, or how to filter windows with expressions, something that I do a lot on my i3config .
And my biggest issue, and this one seems to be with wayland in general is that it seems that it is impossible to set my displays to extended more, that is turn the 3 displays that I have into a single display which I use with some games.
i3 isn't perfect either, I actually had to fork it and apply a patch that fixes and issue that I have that hasn't been merged yet either.
I will list all my issues with sway anyway, hopefully somebody out there notices it and fixes them:
https://github.com/swaywm/sway/issues/8000
https://github.com/swaywm/sway/issues/8001
https://github.com/swaywm/sway/issues/8002
https://github.com/swaywm/sway/issues/8191
And all these bugs are the result of less than 2 days in total of use of sway, there is likely more that I haven't run into.
I also had an issue that affected xfce4 apps, but that issue ended up being a dbus-broker
issue that only happens on wayland for some reason lol
I have a feeling I will be on i3 for many many years given all the issues that I've had with sway.
There is usually misunderstanding behind this type of questions. for example "why isn't ilike on macos where it is ~/.Trash" and then one has to explain what XDG_DATA_HOME is and why it makes sense for trash to be there (And that it doesn't have to do with the desktop environment as well).
Or op just lost something important thinking that the trash was somewhere else.
Interesting that manjaro got kernel 6.9 before arch.
This is really bad lmao.
flatpak is bloated mess. It basically installs a whole distro onto your existing distro.
That person is also lying very badly by saying that appimages bloat the system... they are actually even smaller than native packages due to their compression (like for example the entire libreoffice suite being 300 MiB while a native package is 600 MiB).
This is the space that flatpak takes to install firefox, just firefox: https://imgur.com/a/WRcRWIL
While this is 15 appimages, that includes libreoffice, kdenlive and two web browsers: https://imgur.com/a/YxjUYdt
EDIT: After being accused of misleading people by @BananaTrifleViolin@lemmy.world I decided to install firefox, libreoffice and kdenlive to flatpak, just those 3 applications, because I was told sure the deduplication was going to do miracles:
~~https://imgur.com/ExH84gV.png)~~
)~~6.2 GIB WTF** (15 appimages was 1.2 GiB once again kek, how can flatpak be this bad lmao)~~
EDIT2: This actually isn't the real size, I moved the flatpaks to their own partition and checked that instead:
Alright I just moved flatpak to its own partition and checked the size of the partition instead:
with firefox
, kdenlive
and libreoffice
:
Disk (/var/lib/flatpak) 2.69 GiB / 19.12 GiB (14%) - ext4
That’s much better now. But still twice the size that 15 appimages took.
This is with now having firefox
librewolf
brave
kdenlive
and libreoffice
:
Disk (/var/lib/flatpak) 3.40 GiB / 19.12 GiB (18%) - ext4
Still though, the appimages take less space. A by a large margin.
Flatpak is just a bloated mess, even with deduplication:
And this is what flatpak uses with just firefox installed:
Sorry for misleading people, turns out flatpak doesn't use near 3X as much as 15 AppImages when it just has firefox installed (which once again those 15 AppImages use 1.2 GIB). It just uses 1.35GiB when it has a single app kek.
On top of that flatpak is not terminal friendly, you have to start everything with flatpak run org.etc.etc
(this also breaks scripts that expect the simple binary name in PATH).
Flatpak is also non XDG base dir compliant, and they said over and over that they wont fix that issue: https://github.com/flatpak/flatpak.github.io/issues/191
This person is complaining that appimages suck because you have to put the desktop entry yourself, when apps like am
or zap
and appimagelauncher
do it for you lmao. (And at least am also makes a symlink in PATH so it fully integrates the appimage unlike flatpak ever will)
EDIT: That github link is really bad, it even links this article for saying that sanboxing with appimages isn't secure:
https://madaidans-insecurities.github.io/linux.html#firejail
WHEN THAT VERY LINK SAYS THAT FLATPAK ISN'T GOOD EITHER, it even calls out the flatpak devs for it.
We need something like this for home, I hate that programs like steam and firefox place themselves directly into home instead of ~/.config and ~/.llocal.
I even move my personal themes to /usr/share/themes because not everything works with ~/.local/share/themes and needs a ~/themes directory instead.
Foobar2000, it is the only windows app that I miss.
Deadbeef is close but it is missing several features, it can't even encode using more than 1 cpu core lol.
Koss KSC75, I've been using them for almost 10 years now.
I'm pretty sure
sbin
originally meant static binaries and not system binaries lol