Oh absolutely, the wording Adobe used is abysmal in telling you exactly why they did it, but arguably that is the point.
Nobody wants to hear "yeah so we're killing the feature you're using because it's not profitable enough for us anymore", speaking from experience of this happening with certain FOSS projects (where profit is substituted with "Gary wrote this 5 years ago and we haven't seen him in 3 years so I'm going to yoink it before it starts causing bugs since I dont want to spend time maintaining Gary's code"). That's not an indictment of FOSS projects to be clear (free gift horse and all that), but it does show insight in how feature cuts will come across when done for those sorts of reasons.
The other problem is that sites like Kotaku[1] decided to run the story in a decisively false manner by suggesting that Pantone is trying to copyright the color spectrum. The ARSTechnica article is a slightly more nuanced take on that Kotaku article which was blatantly bad faith, but still overwhelmingly missing the point.
Nobody wants to hear "yeah so we're killing the feature you're using because it's not profitable enough for us anymore", speaking from experience of this happening with certain FOSS projects (where profit is substituted with "Gary wrote this 5 years ago and we haven't seen him in 3 years so I'm going to yoink it before it starts causing bugs since I dont want to spend time maintaining Gary's code"). That's not an indictment of FOSS projects to be clear (free gift horse and all that), but it does show insight in how feature cuts will come across when done for those sorts of reasons.
The other problem is that sites like Kotaku[1] decided to run the story in a decisively false manner by suggesting that Pantone is trying to copyright the color spectrum. The ARSTechnica article is a slightly more nuanced take on that Kotaku article which was blatantly bad faith, but still overwhelmingly missing the point.
[1]: https://kotaku.com/photoshop-pantone-color-plugin-adobe-crea...