/tech/ - Soyence and Technology

i3, dwm

why don't you want to use wayland?

>>30804
because being a contrarian is aryan or something like that yeah

SonicDE is going to try to maintain KDE but with Xorg support

>>30808
I've had almost no issues with kde wayland, theirs is the most complete compositor imo and even xwayland hasn't given me issues, just switch to xfce if you have an actual use case

Trinity

>XFeces is nice but hasn't been updated in 2 years.
>MATE I've never used and it also hasn't been updated in 2 years.

And? What's the problem with not pushing new releases for 2 years if the
software works? Moreover, no fresh releases != abandonware: for example, XFCE's
git repositories are still active with latest commits pushed less than several
days ago.

>LXQt works fine but looks like Indian technology.

LXQt is modular and customizable, you can even swap its window manager for
something else if you want to.

>Is the final solution just to give up on updates? There's also just staying on
>an older version of Plasma with Xlibre anyway.

Trinity is a time-proven and maintained KDE 3 fork, you can check it out. Also,
SonicDE exists, which is a recent fork of current KDE that backports
Wayland-only functionality to the X11 version of the DE. If you want to stop
updating at all, you can statically compile needed KDE software and just
continue to use it regardless of the versions in any repos, though the
compilation process may be tricky, I suppose.

>>30800 (OP)
>XFeces
>LXQt
>MATE
You answered your own question.

What's wrong with Xwayland? Care to elaborate what it can't do?

>>30884
this is a loonix fan, xhey always complain about something but WILL NEVER explain why

>What's wrong with Xwayland? Care to elaborate what it can't do?

Using Xwayland inside a Wayland compositor is not the same as using a
standalone X11 server. I'm not the OP, but from my experience (about a year
ago), Xwayland cannot be called a silver bullet even for running X11 apps: it
leads to bugs in some software or just prevents it from working at all; for
example, popup windows were broken for me in the Audacious audio player and
QCAD crashed immediately (though at least the latter was fixed in recent
versions, AFAIK).

Some more noticeable things (from my amateur viewpoint):

- Pretty much all Wayland compositors do not have as good hardware
compatibility as X.Org does, especially in the case of old NoVideo GPUs—the
session may be unusable at all, therefore if we only had Wayland,
this-potentially useful-hardware would have turned into an e-waste (at
least in the context of desktop usage)

- Almost all Wayland compositors are written with Linux in mind, therefore
porting them to different operating systems is a tough task (not really a
problem for Linux users, obviously, but this has a bad impact on *nix system
family overall)

- Wayland ecosystem is fragmented; to provide a short example: many utilities
made for KWin, Mutter, or wlroots-based compositors just *won't* work on
other compositors. Just imagine how things would suck on X11 if each of dwm,
awesomewm, Openbox, Xfwm, etc. implemented their own incompatible X server
with a custom set of extensions. Nontheless, I must say that recent versions
of the River compositor look promising in this regard; it would be
interesting to write a WM for it

- Wayland pointer handling standards suck ass: they lead to noticeably
(sometimes ridiculously) worse input lag in many scenarios. This is the main
reason why I didn't keep Wayland on my main desktop: when I'm at it, I use a
mouse all the time and every single Wayland compositor I've ever tried
delivers an inferior experience in this regard. However, it's in my backlog
to tinker in this direction, because it's the only big issue in Wayland for
me and I would like to take a crack at examining and fixing it

To be fair, there's also a plenty of cases where Wayland is *superior* to X11;
the main point is that things are not black and white.

>Some more noticeable things (from my amateur viewpoint):

Self-corrected version:

"Digressing from Xwayland specifically, here're some noticeable troubles in
Wayland itself ([…]):"

Or something like that. Parts of the reply were rephrased poorly during the
writing, but its point should be comprehensible.

>>30916
>>30917
i wish someone did this type of explanation when it comes to systemd, most just say its le bad and glowie goyware but never explain why

>>30916
>do not have as good hardware compatibility
Wayland doesn't interact with hardware u dumbass nigga, kernel (Linux) does. Devs write drivers for kernel not compositor

>>30800 (OP)
dude just move to wayland its not that big

>>30800 (OP)
XFCE won bruh

>>30982
>not ricing xfce
Marge?

i use wayland with mangowm and its so nice just switch to wayland chud

>>30982
Hideous fucking desktop environment

>>31030
evedoe I literally riced my taskbar
>>31032
wayland works like ass with my old nvidia gpu you faggot
>>31033
what about it? the settings panel true but everything else is ok right? I mean the only thing you can judge is the desktop background and my taskbar. its much like gnome functionalitywise but less buggy and its more lightweight than kde.

>Wayland doesn't interact with hardware u dumbass nigga, kernel (Linux) does. Devs write drivers for kernel not compositor

- https://www.phoronix.com/news/XWayland-Drops-EGLStream

- https://github.com/X11Libre/xf86-video-mga

- https://github.com/X11Libre/xf86-video-voodoo

- https://github.com/X11Libre/xf86-video-suncg3

>Wayland doesn't interact with hardware u dumbass nigga, kernel (Linux) does. Devs write drivers for kernel not compositor

Also, though I don't know the exact technical details about this, Wayland sessions and their native apps work like ass with old NVidia GPUs-that's just a fact. I've tried GNOME Wayland and KDE Plasma 6 Wayland myself on a PC with GeForce 7025-they barely even worked, produced violent artifacts, and became almost completely static after some time, if I rememeber correctly. This spectacle reminded me how I tried to play Portal 2 on my FX 5200 back in the days, kek.

>>30800 (OP)
i use vxwm (glorified dwm) because (You) are trans btw

>>30800 (OP)
i use amiwm because im amigaryan

>>31049
The issue is Wayland uses different APIs that aren't implemented properly or at all in older hardware

>>31048
Drivers interact with kernel nigger

>doesn't know what a driver is award

I mean that the display server needs to know how to interface with drivers
provided by the kernel. If the driver doesn't conform to APIs addressed by the
server, they won't work well together. At least that's roughly what I remember
from theory.

>>>31048
>Drivers interact with kernel nigger

That's what a nigger would do: curse at others.

wayland is aryan thoughie
only shitskins use x11