The technical merits of Wayland are mostly irrelevant (utcc.utoronto.ca)
In response to Wayland Breaks Your Bad Software...
![](https://kbin.cafe/media/cache/resolve/entry_thumb/e9/8d/e98d856899804d592ec2f2eb279987e621eea7179e711145945fb64309594b6d.jpg)
In response to Wayland Breaks Your Bad Software...
In my entry on how HTTP has become the default, universal communication protocol, I mentioned that HTTP’s conceptual model was simple enough that it was easy to view it (plus JSON) as an RPC (Remote Procedure Call) system. I saw some reactions that took issue with this (eg comments here), because HTTP (plus JSON) lacks a lot...
The reality is that reliable backports of security fixes is expensive (partly because backports are hard in general). The older a distribution version is, generally the more work is required. To generalize somewhat, this work does not get done for free; someone has to pay for it....
I wholeheartedly agree with this blog post. I believe someone on here yesterday was asking about config file locations and setting them manually. This is in the same vein. I can't tell you how many times a command line method for discovering the location of a config file would have saved me 30 minutes of googling.
utcc.utoronto.ca/…/ReportConfigFileLocations
utcc.utoronto.ca/…/ReportConfigFileLocations