Why do software manufacturers always insist on changing things, and fixing things that aren't broken?
A friend of mine who lives here on Manana Mesa is a retired software engineer who worked for a major software company for a long time. Here's his take on the question:
This company hires software engineers on the basis of their specific talents, and how those talents are applicable to the specific piece of software that they need to develop.
Many months, even years sometimes, are spent perfecting and testing the code. When the software is ready for the market, the engineers' job is essentially over. Rarely, though, are they assigned to another project. Generally, they have to maintain the software, fix bugs, and develop updates that technology and the marketing department demand.
Although these tasks could be assigned to lower-echelon coders, the software manufacturer wants the engineers to stay on the same project. Even though they don't have very much for them to do, the software manufacturer doesn't want them to go work somewhere else! The engineers know where all the bodies are buried, and it could be bad for business if they went to work for a competitor.
So, to keep the engineers busy and suitably entertained, they ask them to keep tweaking the software. Move buttons around, change the icons, invent some new menus, etc. All these changes have to go through the marketing department for approval. Most of them are rejected. But a few are retained. Some on the basis of their usefulness and marketability, others just so the engineers will feel useful and won't seek employment elsewhere!
So that's the story from someone who has been there. It's a small consolation when your favorite piece of software has moved all the buttons around!