I thought I'll make this thread for all of you out there who have questions but are afraid to ask them. This is your chance!
I'll try my best to answer any questions here, but I hope others in the community will contribute too!
I thought I'll make this thread for all of you out there who have questions but are afraid to ask them. This is your chance!
I'll try my best to answer any questions here, but I hope others in the community will contribute too!
A wayland compositor and tiling window manager. The lead developer of the project is a Polish transphobic workaholic.
If you understand how shell scripting works you can easily automate menial tasks. CLI is also an interface shared by all operating systems so if you know how to work around in a shell you're not bound to any particular workflow/desktop GUI. Keep using GUIs though, they exist for a reason.
Both are display protocols that are in charge of displaying graphics to your screen. Xorg is over 30 years old while wayland is only about 15 years old. The polemic about xorg was that the codebase was unmanageable and the design architecture of the program was inherently flawed (example: screenlocker getting access to your entire screen including apps and desktop, making writing malware for x11 a 3 line python script). X11 was designed during a time when people were using actual real life terminals and mainframes. Wayland is much more modern and akin to how modern graphics APIs are handled (for the most part)
Wayland at its core has and always will be design by committee so a lot of the arguing is necessary (though sometimes long-winded) to make sure to not repeat xorg's mistakes. Protocols take months if not years to be merged into wayland and those protocols have to be implemented by wayland compositors themselves rather than sharing 1 program altogether like with xorg.
Watch this video for more information, explains it much better and is from an actual wayland board member.
Why YOU should write a Wayland compositor – Victoria Brekenfeld – HiP22 Berlin