I take a view in between of the quoted article and the video it criticizes. There are costs to changes. The key, to me, whether those changes are outweighed by

I take a view in between of the quoted article and the video it criticizes. There are costs to changes. The key, to me, whether those changes are outweighed by functionality improvement, as on average perceived by users. There will always be folks who do not like the change, but if the majority of the users like new functionality (maybe after a bit of griping), or most strong advocates among users love it, this is probably a change for the better. Unfortunately, many software changes are done without bringing the benefit for the users (e.g., "we are switching to framework/model X, so UX is now different; deal with it"). Those changes are pretty hard to justify. Not always impossible (e.g., you may have reached the limits of older design and have to spend a lot on devops, etc.), but hard and for those cases the company should bend over backwards to minimize pain for users. My 2c.