3 ms·
Your memory of config file nightmares (I had them too) is a decade old now. X11 works without config for the vast majority of users. Yes it took a while to get
by SoftTalker 3y ago
Your memory of config file nightmares (I had them too) is a decade old now. X11 works without config for the vast majority of users. Yes it took a while to get there, but it's been there for a good while now and not really anything for Wayland to point at as a differentiator.
- lmm 3y ago> Your memory of config file nightmares (I had them too) is a decade old now. It's at least 2 decades old, if it was ever a real problem in the first place.
- justinclift 3y ago> ... if it was ever a real problem in the first place. It definitely used to be a huge pain in the arse. There used to be pages after pages after pages of random "HOW TO ..." style guides for people to configure X11 config files around the net (many just working for specific hw). It was an incredible mess, with pretty much nothing positive about it. ;)
- mtlmtlmtlmtl 3y agoI've been using Linux for 20 years now and I've never needed more than 5 lines of Xorg config, only a couple lines of which has had meaningful information.
- vetinari 3y agoI've been using Linux since Slackware 3.0; at the time, there were X servers that were specific to a certain card manufacturers/chipsets and you symlinked the correct one. Then you configured xf86config.
- justinclift 3y agoMaybe I was just one of the many er... unlucky ones then. ;)
- MattPalmer1086 3y agoIt was definitely a real problem. Things would work for a while and then break. Sometimes you had to choose between one thing that worked and another. I spent many unhappy hours tweaking X config. But it was indeed around 20 years ago that it was an issue.
- andrewaylett 3y agoIndeed, given it's often the same developers working on both, a reasonable amount of the effort put into getting X to work without needing configuration was people actually working on Wayland but also taking the time to pull X along for the ride where possible. X has a lot of code in it which needs to be elsewhere in the design envisaged for Wayland. Once support (for example, for kernel mode setting) is available for Wayland to use it, it makes a lot of sense to also use it with X.