builds.sr.ht or how to see if some piece of software works on a random OS, including BSDs and if it doesn't being able to fix it via ssh-in. Always love that feature.
wayland and xscreensaver: - Sadly very unlikely to easily happen due to human issues - It's been gross misconceptions on wayland for about 3 years - If XScreensaver wasn't developed behind closed doors I'm pretty sure it would have been done 8~5 years ago as some embedded devices were shipping with Wayland and without X11 - Last article to me reads like "I obviously haven't done my research nor participated but you should do this, even if your stuff has been getting stable enough to be the default on several distros". This is an awful stance to have, at least it should be close enough to what he wants in most compositors. - He should be aware of wayland having different implementations and so some of them being better, at least subjectively. Quite like how jwz himself described some X11 implementation differences from the 90's. (While now it's almost just XOrg, to the point where most people heavily conflate the two together)
wayland and xscreensaver: - Sadly very unlikely to easily happen due to human issues - It's been gross misconceptions on wayland for about 3 years - If XScreensaver wasn't developed behind closed doors I'm pretty sure it would have been done 8~5 years ago as some embedded devices were shipping with Wayland and without X11
> It is not far-fetched to imagine a future in which sites simply refuse to serve pages to users running free browsers or free operating systems. If WEI isn't stopped now, that future will come sooner than we think.
Which is also pretty much my point of view.
> We urge everyone involved in a decision-making capacity at Google to consider the principles on which the web was founded […] >And if they don't? Well, they ought to be ashamed.
Simply ashamed? We'll just merely middle-finger at the direction of Google while they're locking down what used to be one of the most open platforms? <sarcasm>That's sure going to be effective</sarcasm>
I quite wish wayland wouldn't be compared to systemd so much…
Wayland is an evolution from X11 by it's own developers and pretty much all desktops environments involved. Migration to it can be pretty gradual and smooth, in fact you can still just keep using Xorg/TinyX/… without added issues, just bitrot starting to appear because of new hardware.
Meanwhile Systemd is pretty much one-sided and it's also an implementation that forcefully shoved itself into the ecosystem. It broke a ton of things and still regularly breaks things.
I quite wish wayland wouldn't be compared to systemd so much…
Wayland is an evolution from X11 by it's own developers and pretty much all desktops environments involved.
Also take me as pedantic but I'd maybe a difference between: - Wayland: protocol - libwayland: helper library, you can choose to not use it for your own stuff (but others will likely depend on it) - whatever compositor/display-server you're thinking about (Apache isn't HTTP) - user applications (Google Chrome isn't HTTP either)
(And yes the wayland ecosystem has a lot of udev+linux-isms, basically because the folks that do not want udev/linux-isms didn't care about wayland for 10+ years, I was part of those btw)
Also take me as pedantic but I'd maybe a difference between: - Wayland: protocol - libwayland: helper library, you can choose to not use it for your own stuff (but others will likely depend on it)