I want something simple and powerful, and btw what panel/utils you use on wayland?
>>110019934idk, whatever comes with your DE.
>>110019934>What Compositor you recommendcompiz existed 20 years ago. talk about relevant technologies like "what intent router do i use" or "what intent bridge do i use on my phone" https://github.com/loosestrife/matchbox202x
I use hyprland and dank material shell because they're the only two professional projects. KDE crashes too much and Gnome is a fucking joke and I'm at the point where I'm going to start using AI to rewrite GTK tainted applications in Qt just to remove the possibility of anything produced by that cursed outfit from touching my machine.
I don't even know what a compositor is lol
sway, labwc, or niri, depending on which layout mechanism you prefer
>>110019934>simple and powerfulI like mangowm for its master/stack layout and tag system. it can also do scrolling if you like that. but I feel the compositor isnt that relevant, theyre mostly all wlroots wrappers except niri>btw what panel/utils you use on wayland?noctalia or DMS, they're everything you need and nothing you dont in one sleek package, no longer do you have to jank everything together manually
>>110021895its basically the server on the wayland side, where you have the x.org server on x11 side
river
>>110019934I use Sway, because it is simple and lean, basically i3 tiling wm as a Wayland compositorIf you want bling, Hyprland is easily the best
niri with noctalia it just werks
>>110019934hyprland with quickshell.
>>110021895the window manager gives the windows their final coordinates and z order. the clients draw their contents. the gpu draws it all asynchronously. the only components you care about and want to personally reimplement are the window manager and intent router, because those implement user policy. you also want to implement a bridge, to bridge your x session to your favorite network. your bridge will depend on packets having xchannel framing and will have to implement xchannel and xblob nat, then you can access the xintent and xaudio infrastructure
>>110019934No compositor. That leads to the best performance, better smoothness and lower latency. All wayland compositors stutter when your gpu usage is at 100% and you also want to record the game. This doesn't happen on x11 without a compositor.
>>110023150>>110023381>x session>x11Uncs, it's 2026
>>110023556
Stop being an indecisive chud and try one out, at least wayland makes it dummy simple to switch compositors. Its alll just another command. And configs are separate so you can switch seamlessly.
use mutter (chrome) or kde (firefox). the rest are memes. it's chrome vs firefox situation since the "protocols" are useless and retarded. it becomes obvious when wlroots tried to create a common floor and even steam, both boycotted (directly or indirectly) by redhat. Revealing the obvious, they aren't retarded and built trash slop (whyland) thinking it were "safe" and "modern". It was just to earn power, being useless and retarded was a nice way to achieve it.
>>110022731>>110023150The final link in the chain that actually deals with how frames are presented to the display and handles VSync and so on? IDK, I'm fucking retarded.
>>110021895it lets you do gay transparency shit, I assume (I don't have one)
I've been running into more things that Wayland can't do than it can. I thought it was the future?The only benefit so far is frosted glass windows, which is cool, I guess, but not really worth ditching X11.
>>110021895Any time any program wants to show anything on the screen, it contents to the Wayland compositor (a Wayland server, essentially), and then speaks to it using the Wayland protocol. In particular, the program asks the Wayland compositor to create a window or something like that. The Wayland compositor (Wayland server) is entity that directly decides which apps get to have windows, where they're located, etc, and then asks the kernel to actually draw them on the screen
>>110027087I don't want to tinker tranny with a bunch of half baked projects, I mainly used bspwm or xfce in muh linux life, I want something similar. Though after a long time away from tiling window managers and using xfce with its native stacking wm; I realized that the best UX is not a tiling nor a stacking wm, but a hybrid where you can have the stacking when you want, and you can also tile, but not like other WMs, every window is stacking by default, but when you tile (e.g. terminal with a browser window with docs) that tiling is only for those 2 windows, and when you switch to other windows they show their view; so the tiling is only on that specific stack, when for example I switch to B I would see B & C, but when I switch to A I would see only A. This doesn't replace workspaces, as they can be used to organize different stacks, like one stack is for a project, and the other for another.Idk if I can implement this kind of layout in any wayland compositor?
>>110029224it's similar to a scrolling WM like niri, but I'm not really a big fan of scrolling, I'd much rather deterministically switch to the stack I want.
>>110029224uhh you mean something like this? sway can do this. it supports all sorts of layouts and is the closest thing we have to the 'canon' wayland wm implementation
>>110029224scrollers like mango or niri can do this, just set window A's width to the width of your display, then switch between A and C
>>110019934https://codeberg.org/ezemtsov/ewm
>>110019934I tried loads of panels. The LXQT one was my favourite after I let an LLM rice it for me.
>>110030848Of course Emacs can do that.
>>110020326>>110024920>https://github.com/loosestrife/matchbox202xIsn't this basically Arcan except less ambitious? And also in JavaScript (wtf).
>>110019934Labwc
>>110019934the one you wrote yourself, of course
>>110023556It's still faster and has fewer bugs.
>>110019934xorg
>>110023556it's 40 years old and is still smoother for desktop use and gaming, why should I not use it?
>>110027909You can have that frosted glass on x11 to, with a fork of picom
