From Wikipedia, the free encyclopedia
Linux is a family of open source Unix-like operating systems based on the Linux kernel, an operating system kernel first released on September 17, 1991 by Linus Torvalds. Linux is typically packaged in a Linux distribution (or distro for short).
Distributions include the Linux kernel and supporting system software and libraries, many of which are provided by the GNU Project. Many Linux distributions use the word "Linux" in their name, but the Free Software Foundation uses the name GNU/Linux to emphasize the importance of GNU software, causing some controversy.
Community icon by Alpár-Etele Méder, licensed under CC BY 3.0
The first concrete example mentioned (18 minutes in) seems to neatly sum up the difference in design philosophy.
X11: Four different keyboard input focus modes, where two would suffice.
Wayland: Only one input focus mode, where two would suffice.
Why YOU should write a Wayland compositor
I don't really know how to do that
Hahaha I also dont think we need more of them. But improving the already existing ones for sure is good!
We DEFINITELY need more of them. There's Hyprland, Qtile, River, DWL and Sway on the tiling side. There is no real alternative to BSPWM (though river uses a similar config style) or to HerbsluftWM (though I don't know anyone that uses it, but still), or an alternative to AwesomeWM, or XMonad (though the XMonad devs are willing to pay someone to work on porting XMonad to Wayland)
There's also Strata, Niri, and to some extent Cosmic. My problem has been that they tend to be very opinionated and limited in the customization of the layouts. Having used XMonad for a long time, I may be a bit spoiled in that regard...
I do think there's a middle ground for configuration without requiring programming skills, which can be off-putting for many users. After all, most layouts are just a combination of rows and columns. 😛
River is great for layouts. My main issue is that some of ghese projects need furthed stability and others are still adding features, changing and breaking configs, which could make for a painful experience because of version mismatch between distros, for people like me, who constantly hop between a few distros and can't settle on either of them because none are perfect.
Yeah, lack of XWayland support has been an issue for me. Versioning the config API is something I've been considering, or at least ensuring backwards compatibility.
I'd be interested in other ideas or pain points you've experienced. Not to suggest I'll ever have something production-grade, but my hope is to get to a point that I have a working daily driver and potentially share it with others.
I don't really know how to do that
Hope it helps!
I actually started working on one a few weeks ago. It's amazing how easy it was to get the basics working. Still a long way to go, but it's a fun project in the meantime and hopefully can result in something that supports my desired flow.
It can be useful to try to make one just to learn how it works
Respectfully, I will just leave it to those who know how it works and are generally better at coding. My result would anyway be subpar, unstable and inefficient.
If you want to tweak something that works out of the box, maybe check-out Louvre:
https://github.com/CuarzoSoftware/Louvre
It is C++ which some will love and some will not.
Getting to a few fully working Wayland compositors has been a long and painful journey. Once we get there though, I am pretty excited to see the innovation it enables.
The talk mentions that there was effectively only one implementation of X due to the complexity. There are already quite a few independent implementations of Wayland. That still kind of sucks for the moment but at some point it is going to be awesome.
Or cosmic-comp, based on her work on smithay, also fully working!
Lol, wtf?