isnt it the same with arch?
I once to helped troubleshoot an EndeavourrOS user.
during the process I discovered that their kernel parameters were being reset with every kernel update, this was because Endeavour was using dracut instead of mkinitcpio…
especially if you ever do a hard-shutdown, prone to power-outages, etc. It will scramble your system files.
Btrfs is made precisely so that a power outages don’t do that! and you don’t end up like ext4 with bad superblock nonsense.
Been using Btrfs for over 3 years at this point, 0 issues and over 400 unsafe shutdowns: https://imgur.com/a/AKXFdKb
In fact it was able to detect when my previous ssd was dying, I thought Btrfs was spewing nonsense until the next day when smartctl began to report issues as well lol.
I started linux with wayland and i have no clue why it’s such a controversy lmao.
I recently ran into an user that rarely used x11. We were testing lsfg-vk, and right now it has a bug that when you close the game it most of the time it hangs and doesn’t quick properly.
The person complained about having to open the terminal to kill the app when it hangs and I had to explain that this is not an issue for me because I use xkill which they never knew was a thing that avoided that whole mess of having to open a terminal to kill a window.
But anyways, not a big deal if you can no longer use xkill, it is a very handy tool that saves a lot of key presses but not a vital thing in the end.
The big issue holding me on x11 is that there is no way to merge multiple displays as one, something that on x11 is a very simple xrandr --setmonitor is impossible on wayland, there is no way to do it.
There are lots of issues with Wayland. They will be fixed
Remind me 2030 if these issues I have get fixed:
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 I later learned the reason sway is using capabilities is to fix performance issues, which yeah still has several…
One issue the wayland proponents fail to notice is that the ecosystem itself is fragmented, you have several DEs/WM with their own implementations and bugs that will likely never be fixed.
I’m an i3wm user, my only option to switch to is sway, doesn’t matter if some of the issues I have are fixed in kwin or mutter, it has to be fixed in sway.
But most Linux desktop users use Wayland already.
Most desktop users use windows, and they are happy with that, why don’t you stop using linux and move to windows?
Everyday there are more and more apps that are Wayland only. Before 2030, that list will include all GNOME and most GTK apps. Are people really going to give up all these applications because of some obscure advantage they perceive in X11?
https://aur.archlinux.org/packages/12to11-git
people writing these articles do not realize that they are already in the minority and have already been left behind.
Doesn’t remove the fact that wayland still sucks 😆
Wayland support for multi-monitor configurations is better than X1
Alright, how do I merge the 3 displays that I have as one then?
https://www.reddit.com/r/wayland/comments/108dgwc/combine_monitors_to_single_screen/
Whatever performance degradation you claim to experience is also a “you” thing
It is one of the reasons why Eden disabled wayland by default but sure thing, just a me thing 😆
There’s an underlying issue with your setup.
Yeah, it is called sway.
I don’t even use a login manager, directly login from tty and just launch each respective game, sway is able to use my i3 config directly, the only change in this setup is the window manager.
Also note, this performance issue is not present in BeamNG, it only happens with Eden, citron, etc (all yuzu forks).
Wayland does seem to work well with Intel graphics, at least.
heh https://gitlab.freedesktop.org/mesa/mesa/-/issues/13319
tbf this is not fault of wayland but gnome deciding to make GTK4 use vulkan by default on wayland.
A lot of the new modern users are into gamin
I can’t use wayland for gaming because I do multi-monitor gaming, and something that was a very simple xrandr --setmonitor is impossible in wayland…
I 100% have seen performance increases and stability increases after switching to Wayland with regards to gaming workloads.
All I have seen so far is that I get half the fps I get on citron/eden on sway vs i3wm.
They are also fed up with the wayland bugs and decided to force xcb everywhere, one of the bugs is that the app just crashes on wayland gnome, it does not happen plasma, or sway, or any other place, just gnome.
.mozilla : “Oh but I AM special”
You would think that thunderbird would use ~/.mozilla as well but nope. It is ~/.thunderbird 🤣
Check my dotfiles https://github.com/Samueru-sama/dotfiles
0 hidden files, everything is in ~/Local.
Recently added this hack for ssh: https://github.com/Samueru-sama/dotfiles/commit/7e1f8bd3173da563731aea6db9efbf26a2b23e72
Most flatpak runtimes only have 2 years or support, or in the case of the GNOME runtime 1 year lol.
So yeah you have a “stable” target for a few years at most, then the new runtime comes, breaks something and the project ends up using an EOL runtime, like OBS or more recently prusa slicer.
When did this happen? what error did you get?
Btrfs will explicitly go read only when it detects corruption, which is a good thing, with EXT4 you don’t know what is going on until it is too late.
fwiw the only time I managed to get info from an user that had “issues” with btrfs, I discovered that what had happened is that they moved the partition that had snapshots, and if you don’t know it, this is catastrophic because this unlinks all the snapshots and suddenly everything would take many times more storage.
The short time I’ve used EXT4 running into bad superblock errors was something that happened almost every week, but in the end I was always able to repair the disk and recover everything.
I’m from Venezuela, power failures are common here.