The most beautiful (as in "beautifully evil") aspect of it is that you don't need to do anything to make this "planned obsolescence" happen. You just develop stuff under time pressure (of course) while pretending those slightly older machines don't exist. So if an old driver gives you grief because it needs some find/replace work, you just don't care, you yank it wholesale.
Note that open source projects employ the same tactics. Act I: "oh, we made our thing compile in Wayland-only mode, but don't worry, you can still configure --with-x11". Act II: "Now that most distributions we think matter are shipping Wayland-only builds, we deprecate the X code". Act III: "Oh the --with-x11 started causing compilation errors or bugs, we decided to yank it off and also close all 22 MRs that were fixing these exact errors".
So, don't ascribe to malice what can be ascribed to CADT and budget cuts.
I won’t say I like this phenomenon in oss , but isn’t it a bit of what’s supposed to happen? ie if enough people care about certain code paths working , they pony up and make them work?
Note that open source projects employ the same tactics. Act I: "oh, we made our thing compile in Wayland-only mode, but don't worry, you can still configure --with-x11". Act II: "Now that most distributions we think matter are shipping Wayland-only builds, we deprecate the X code". Act III: "Oh the --with-x11 started causing compilation errors or bugs, we decided to yank it off and also close all 22 MRs that were fixing these exact errors".
So, don't ascribe to malice what can be ascribed to CADT and budget cuts.