Speaking as a developer outside of the gaming world, the answer to the question of “why can’t the program do this?” is that when the program was written, nobody asked for the program to do that. Poorly specced applications with insufficiently documented requirements (and unrealistic timeframes for completion) are the bane of all developers. The reason why we ask users to justify making changes to an application, is because (at least in my experience), developers have WAY more work on their plate than they can even begin to think about getting done, and the biggest problem faced as a developer is how to prioritize user requests. And as somebody who doesn’t use the program in their day to day work, having a good idea of why it’s important to the workflow of the actual users is important. It’s not the developers being lazy and not wanting to make your changes (at least, not most of the time, lol), it’s the developers trying to figure out which of the hundreds of outstanding user requests should be tackled next. And yes, the more people that have the problem, the more likely it is to be prioritized.
