unique_hemp

@unique_hemp@discuss.tchncs.de

This profile is from a federated server and may be incomplete. Browse more on the original instance.

unique_hemp,

WMs typically do not include stuff like a custom GUI for system settings and do not have a suite of GUI software associated with it (think Kate, Konsole, Dolphin etc) - it is just a piece of software for managing windows, you have to put the rest of the desktop together yourself.

unique_hemp, (edited )

Some distros have editions with a WM (usually i3) as a default, yes. These editions tend to come with some basic config so it’s more usable out of the box. But you can also install WMs side by side with DEs and then switch in the login manager (GDM, SDDM), just the same as you can install multiple DEs on a system. You could also install a headless version of a distro first and then install only the WM and whatever other tools you want on top of that. Basically all system settings can be changed through config files or CLI programs, for some things like audio and bluetooth there are good DE-independent settings programs like pavucontrol.

You , for example, but that’s pretty messy, IMO.

As for advantages, WMs are usually very keyboard driven, you pretty much never have to touch the mouse. They also tend to be fairly light weight and use little RAM. My favourite i3 feature is that workspaces are per-monitor, so I could easily move multiple windows between monitors and not lose the way they are set up.

As for disadvantages, changing any system settings tends to be a research project, because there is no centralized solution, it’s even worse than Windows in this regard. Personally this is the main reason I switched back to KDE from i3. I could also never get theming to work quite right.

unique_hemp,

It’s fine with the beta driver, so still not fine by default.

unique_hemp,

Native games need to add client side decorations to be usable on Wayland Gnome. Currently most games just run in XWayland.

unique_hemp,

I’ve seen enough blurry software on Windows to know this is not quite true 😅

unique_hemp,

The way I see it, GTK is really a framework for building cross-platform GUI apps. Then handling display server compatibility makes perfect sense to me.

If this was meant to be a dig at Wayland, I’m pretty sure GTK also needs explicit and direct support for X11, Windows and MacOS. It just already exists.

unique_hemp,

The flipside of this is that you as the BDFL are not in any way entitled to community contributions. If they decide to not like your furry board, they are free to fork the project, but splitting the development efforts could very well kill both projects, so sometimes it is better for the project to listen to the community.

Explicit sync Wayland protocol has finally been merged! (gitlab.freedesktop.org)

Since nvidia drivers do not properly implement implicit sync, this protocol not existing is the root cause of flickering with nvidia graphics on Wayland. This MR being merged means that Wayland might finally be usable with nvidia graphics with the next driver release....

unique_hemp,

Well, this is the root cause of this specific issue if you treat nvidia’s part of the stack as some barely changable black box (which is what it is right now). It’s not that I disagree open source drivers would be better, I just already own an nvidia GPU :/

unique_hemp,

Nouveau should have already been fine, this should fix the proprietary driver’s issues. AFAIK this is a core issue of the proprietary driver, so should affect all cards.

I tried Wayland on my 16xx series GPU, Electron apps were only annoying, but games were unplayable. The desktop itself and Wayland native apps worked fine, though.

unique_hemp,

Yes, for that to change we have to wait for the NVK based driver - nova.

unique_hemp,

Yes, but that’s bound to be merged quickly, the protocol itself was the main holdup from what I understand.

unique_hemp,

Plasma 6 X11, 550 proprietary driver.

unique_hemp,

Desktop 1660S

unique_hemp,

Maybe if your games are Wayland native or you’re still running the 535 driver? I saw fbdev=1 as a workaround, but that made things very jello-y.

unique_hemp,

I saw a comment from an nvidia dev somewhere that XWayland support is enough to resolve the flickering, but compositor support is needed for best performance.

unique_hemp,

Yeah, still gonna be a couple of months, but that is the last signifficant issue for me, fingers crossed.

unique_hemp,

SELinux is a pain on Arch, it actually working nicely could be viewed as Fedora’s killer feature.

wiki.archlinux.org/title/SELinux

unique_hemp,

No, because this is common terminology that has no reason to be messed with, even if it is technically unclear.

AMD GPUs are cursed for me

Each time I try AMD graphics, something is fucked for me. Back with fglrx, fglrx just sucked, so I used Nvidia. Then I had an AMD right around when they finally had opensource drivers, but it was still buggy as hell. So I went with Nvidia again (first a GTX 790, then a GTX 1060). In the meantime I had a new work notebook where I...

unique_hemp,

Yeah, until this thread I was convinced I should stay away from nvidia GPUs when building a new PC with Linux in mind, but I’m not so sure anymore.

unique_hemp,

It’s looking great! I joined just 2 days ago and the communities I subscribed to are already looking much more lively today. Thanks, Reddit blackout!

Also written in Rust, btw :)

  • All
  • Subscribed
  • Moderated
  • Favorites
  • fightinggames
  • All magazines