logo

blog

My website can't be that messy, right? git clone https://hacktivis.me/git/blog.git
commit: 7649c2043a90330b36d99bd129728b4e0a878d46
parent 130b1783569654bd8fcd6a2c657a5f67484485ba
Author: Haelwenn (lanodan) Monnier <contact@hacktivis.me>
Date:   Tue,  2 Feb 2021 14:33:36 +0100

articles/Why I embraced Wayland: New Draft

Diffstat:

Aarticles/Why I embraced Wayland.shtml15+++++++++++++++
Aarticles/Why I embraced Wayland.xhtml32++++++++++++++++++++++++++++++++
Mfeed.atom11+++++++++++
3 files changed, 58 insertions(+), 0 deletions(-)

diff --git a/articles/Why I embraced Wayland.shtml b/articles/Why I embraced Wayland.shtml @@ -0,0 +1,15 @@ +<!DOCTYPE html> +<html lang="en"> + <head> +<!--#include file="/templates/head.shtml" --> + <meta property="og:type" content="article"/> + <meta property="og:title" content="Why I embraced Wayland"/> + <title>Why I embraced Wayland — Cyber-home of lanodan</title> + </head> + <body> +<!--#include file="/templates/en/nav.shtml" --> +<!--#include file="/articles/Why I embraced Wayland.xhtml"--> + <a href="/articles/Why%20I%20embraced%20Wayland.xhtml">article only(plain XHTML)</a> +<!--#include file="/templates/en/footer.shtml" --> + </body> +</html> diff --git a/articles/Why I embraced Wayland.xhtml b/articles/Why I embraced Wayland.xhtml @@ -0,0 +1,32 @@ +<article xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en" class="h-entry"> +<a href="/articles/Why%20I%20embraced%20Wayland"><h1>Why I embraced Wayland</h1></a> +<p>Some of the folks that knew me from around 2014 know that I wasn't impressed with Wayland and really didn't see the point of it. X11 worked well enough for me and I didn't want to switch to something else, it felt like reinventing new stuff just for the sake of it to me (like systemd and pulseaudio). And I disagreed quite badly on it, sorry for folks related to wayland. Hopefully less and less folks will do this "politically conversative" opinion and actually wonder about the reasonings.</p> +<figure> + <img src="/images/Firefox%20overlaying%20st%20on%20my%20laptop.png" /> + <figcaption>Firefox gliching over the terminal on my laptop</figcaption> +</figure> +<p>Then after some years of applications like Firefox shitting all over the desktop at times, all applications being able to snoop keyboard input with no real solution against that, and the huge last drop that a window manager in X11 seems to basically just be a regular application rather than somehing which defines policy and actually manages windows, probably related to how regular applications can trash your multi-monitor setup back to a single 640x480 screen where it never really restores if the application doesn't do it, I was just done with X11 and it's design of being similar to a Unix where everyone is root.</p> +<figure> +</figure> +<p>Plus <em>actually reading the wayland protocol design</em> rather than only looking at what kind of horror GNOME is doing (as usual) with it and what new toyish demo weston did made me really interested in it and so about a year and a half ago I switched to <a href="https://swaywm.org">Sway</a> on my previous laptop (which is running on a horribly badly supported nvidia GPU where nouveau became somewhat on par with it overall and much better for 2D video acceleration and multimedia plus fewer scary glitches, Fuck You NVidia, thanks nouveau devs for making that laptop last few years longer). +Oh and my phone was already running on Wayland since 2015~2016, as I completely switched to SailfishOS (CyanogenMod destroyed it's own system on my phone and then community on internet), I maybe just didn't knew or ignored that fact as it's not as desktop/laptop. Works really well on it btw, X11 never made sense to me on handhelds, which is yet another point for Wayland. +</p> +<p>All that said,<ul> + <li>I have yet to switch to wayland on my desktop, mostly because XMonad works much better for how I think things than i3 on a multi-monitor setup and VR on Wayland can work but it got apparently stuck at the experimental stage but I could just launch VR stuff in it's own Xorg session anyway,</li> + <li>I have done the quite crazy thing of throwing all of X11 (including stuff like <code>libX11.so</code>) out on my laptop, it means a lack of some applications and some weird shenanigans (like <code>libGL.so</code> having X11 symbols and so <code>libOpenGL.so</code> being the window-system-agnostic one but sadly being from <abbr title="GL Vendor-Neutral">GLVND</abbr> which has yet to appear on systems like FreeBSD) but overall it works pretty nicely</li> + <li>I have yet to resume working on <a href="/git/inaban">inaban</a>, a quite psychorigid wayland compositor on controlling how applications are controlled in the display server (complete opposite of X11 in that area)</li> +</ul></p> +<h2>See More</h2> +<ol> + <li><a href="https://drewdevault.com/2019/02/10/Wayland-misconceptions-debunked.html">Wayland misconceptions debunked</a></li> + <li><a href="https://www.youtube.com/watch?v=HllUoT_WE7Y">"Write a single library to handle all input devices, it'll be easy" they said…</a>: Talk about a linux-induced burden but relates a bit to Wayland on Linux and FreeBSD</li> + <li><a href="https://www.youtube.com/watch?v=RIctzAQOe44">The Real Story Behind Wayland and X - Daniel Stone (linux.conf.au 2013)</a> (00:45:34)</li> + <li><a href="https://github.com/swaywm/wlroots">wlroots</a>: Pluggable, composable, unopinionated modules for building a Wayland compositor; or about 50,000 lines of code you were going to write anyway.</li> + <li><a href="https://swaywm.org">sway</a>: i3-compatible (with few extras) Wayland Compositor</li> + <li><a href="https://git.sr.ht/~sircmpwn/wio">wio</a>: Wayland compositor for Linux & FreeBSD which has a similar look & feel to plan9's rio</li> + <li><a href="https://hikari.acmelabs.space/">hikari</a>: Wayland compositor inspired by CWM</li> + <li><a href="https://wayland-book.com/">Wayland Book</a> by Drew DeVault</li> +</ol> +<p>Yeah… all of that is linked to wlroots, feel free to pass on links from others, I know MATE is planning to switch to Wayland but it's still mostly for the future and I don't know how well wayland works in KDE (probably quite well).</p> +<p><!--<a href="">Fediverse post for comments</a>, -->published on 2020-11-26T19:08:41Z, last updated on 2020-11-26T19:08:41Z</p> +</article> diff --git a/feed.atom b/feed.atom @@ -11,6 +11,17 @@ <!-- new.sh: new articles here --> <entry> + <title>Why I embraced Wayland</title> + <link rel="alternate" type="text/html" href="/articles/Why%20I%20embraced%20Wayland"/> + <id>https://hacktivis.me/articles/Why%20I%20embraced%20Wayland</id> + <published>2020-11-26T19:08:41Z</published> + <updated>2020-11-26T19:08:41Z</updated> + <content type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml" xml:lang="en"> +<!--#include file="/articles/Why I embraced Wayland.xhtml"--> + </div></content> + </entry> + + <entry> <title>real names</title> <link rel="alternate" type="text/html" href="/articles/real%20names"/> <id>https://hacktivis.me/articles/real%20names</id>