Conversation

Notices

1. Embed this notice
   Haelwenn /элвэн/ :triskell: (lanodan@queer.hacktivis.me)'s status on Tuesday, 05-Sep-2023 17:27:56 JST Haelwenn /элвэн/ :triskell:
   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)
   • Embed this notice
     kline 🏴󠁧󠁢󠁳󠁣󠁴󠁿 (kline@mastodon.sdf.org)'s status on Tuesday, 05-Sep-2023 18:00:35 JST kline 🏴󠁧󠁢󠁳󠁣󠁴󠁿

     in reply to

     @lanodan jwz is, in general, a bit of a cock.
     I don't know why people put so much uncritical faith in his stuff.

     When it comes to a lot of his writing, he presents himself as unambiguously correct in all cases and always other people's problems.

     I worry people with this kind of attitude distort the truth, and sure enough in his long series of "I told you so" posts about other screensavers bugs, he neglects to even mention xscreensavers own, despite promoting it as bulletproof one-true solution

   • Embed this notice
     Haelwenn /элвэн/ :triskell: (lanodan@queer.hacktivis.me)'s status on Tuesday, 05-Sep-2023 18:00:35 JST Haelwenn /элвэн/ :triskell:

     in reply to

     • kline 🏴󠁧󠁢󠁳󠁣󠁴󠁿
     @kline The true bulletproof way would have been patching servers like XFree86 for a better screenlocking design, which would have benefited everyone and been much easier to maintain.
     
     Instead he came up with pretty restrictive workarounds for XScreensaver, and even worse wanting others to do the same shit.
     
     IMO workarounds should the kind of stuff that ought to disappear at some point by fixing the issue at the source.
   • Embed this notice
     kline 🏴󠁧󠁢󠁳󠁣󠁴󠁿 (kline@mastodon.sdf.org)'s status on Tuesday, 05-Sep-2023 18:05:56 JST kline 🏴󠁧󠁢󠁳󠁣󠁴󠁿

     in reply to

     @lanodan needing piles of architectural extensions for X11 is, as you know, why people opted to move on to wayland.

     I don't grudge people for wanting to stick with what they know rather than join a vanguard of tech progress - not everyone wants their computer to be a project - but at the same time FUD like this is just FUD.

   • Embed this notice
     Haelwenn /элвэн/ :triskell: (lanodan@queer.hacktivis.me)'s status on Tuesday, 05-Sep-2023 18:05:56 JST Haelwenn /элвэн/ :triskell:

     in reply to

     • kline 🏴󠁧󠁢󠁳󠁣󠁴󠁿
     @kline Which is why I'm also saying that he should have handed-off the linux/X11 side to another developer, where then Wayland would likely have been just another changelog entry, quite like it has been for most software so far.