The real story behind Wayland and X

Really recommend that speech as well since it's give good understanding what's wrong with X11 and why Wayland was created. The real story behind Wayland and X: [VIDEO]

This criticism looks like "free as beer and I know better". 1. The old, mostly working thing waits your commit 2. That new thing can have some help too I recommend developers story about this "mostly working thing" (2014) [1]. It is quite fun and eye opening, he clearly knows his subject better than most of the comments. Wayland demo worked almost from day one. I've run it in 2010 [2]. But we need applications, that is migrating toolkits and this took 10 years. It is very toxic development culture, cancel culture, mob. [1] [VIDEO] [2] [LINK]

It would be nice to reproduce phoronix results. Do they run in GNOME shell? What if I run in Sway? What exactly they expect of Selenium? I've heard gedit startup example. Sorry, I can't continue until you've watched presentation [1] > gedit startup: > 130 blocking InternAtom calls > 34 blocking GetProperty calls > 116 property change requests > blocking because Xlib is terrible > usually spends 25ms waiting for requests > sometimes spends 1428ms [1] [VIDEO]

Daniel Stone, The real story behind Wayland and X (Or, 'Why Everything You've Read in LWN and Phoronix Comments is Untrue') [VIDEO] And directly from ajaxnwnk [LINK] > Moreover, X works for me now and does everything I need. Someone makes pig fly all these years.

Well, you can imagine some evil behind everything if you wish.. Or just look at a technical video about it: [VIDEO] I don’t see these conteos regarding linux, especially goddamn desktop with the minuscule user share. It is literally a hobby thing for some graphics enthusiasts without any sort of money. Yeah sure, red hat or whatever..

> I've seen commentary from people who have worked intimately on both protocols and implementations of both who consider Wayland to have the better architecture. For those interested in details: [VIDEO]

>Ultimately, since I can't go wrong with X and I can go wrong with Wayland, the choice was easy. Keep in mind that Wayland has been designed by people who've been maintaining X11 for years. >it also offers no mode that would work over a network X11 has a huge number of issues when it comes to network transparency. tl;dr is: it's not designed for this, you should use a proper remote desktop protocol instead. More info: [VIDEO] >Of that, EGL even requires Mesa and thus Cgo. That's not true anymore. You can use the DMA-BUF protocol instead of wl_drm. I'm not sure how to export a DMA-BUF without Cgo though… But that's a different issue. If you're going to use the GPU you'll probably need Cgo anyway.

last time I used kde was in 2002. I loved especially kmail and konqueror. Though I have eventually been turned off by the dependency hell of big DE's (not unique to kde and probably only an issue if you compile the DE yourself, ... though also annoying if you have 100+ base-packages/dependencies pulled in just because you want 1 tool). after moving to i3 I find it hard to look back. the level of customization I can do with a tiling WM (also dwm, xmonad etc) is just insane. Makes more sense to me since most of the tools I use are lightweight, e.g. suckless (surf), a complete process tree after login now consists of: ?─┬─?───i3-wrapper───i3 ├─sh───xautolock ├─sh───unclutter ├─sh───dunst───2*[{dunst}] ├─sh───i3bar───sh───python───{python} ├─sh───x-terminal-emul─┬─3*[bash] │ ├─bash───pstree │ └─6*[{x-terminal-emul}] └─systemd─┬─at-spi-bus-laun─┬─dbus-daemon │ └─3*[{at-spi-bus-laun}] ├─at-spi2-registr───2*[{at-spi2-registr}] ├─dbus-daemon ├─dconf-service───2*[{dconf-service}] ├─dirmngr ├─gconfd-2 ├─gvfs-udisks2-vo───2*[{gvfs-udisks2-vo}] ├─gvfsd─┬─gvfsd-trash───2*[{gvfsd-trash}] │ └─2*[{gvfsd}] ├─gvfsd-metadata───2*[{gvfsd-metadata}] ├─pulseaudio───2*[{pulseaudio}] └─tracker-store───4*[{tracker-store}] $> sudo smem -c pss -t | tail -1 606032 ^^^^ as commenter below pointed out this includes processes from other users. the correct figure is smem -c pss -t | tail -1 220678 Use compton if you need some bells+whistles (transparency). If you want to get rid of X.org and use Wayland[0]