I swear people don’t understand planned obsolescence. PLANNED is the key

If I stop supporting a 6-year-old version of something because I have data suggesting hardly anyone uses it anymore, that’s just garden variety obsolescence

If I plan on day one to stop support after 6 years, THAT is planned obsolescence. Same if I just make design decisions such that most of them will break before then.

If I deliberately break old things, that’s not planned obsolescence, that’s FORCED obsolescence.

@calcifer and there is a big difference in how that is communicated as well. For example, if I support a draft standard while the standardization effort is ongoing, and from the very beginning say that I will deprecate and replace with the actual standard once it is ready, then there is IMHO nothing objectionable happening, even though I planned the obsolescence from the start.