Hi Nameless Voice,
That’s not what I’m trying to say, although I see why you see it that way. It wouldn’t be the first time to see this happen in a project.
Usually when you develop a software this massive you tend to find problems of this caliber that are pretty hard to predict when you are designing the fundamentals at the begining, even years and iterations after you still see them comming. So it’s pretty much unavoidable to make this kind of mistakes.
However, it is best to focus in smaller or more affordable bugs that don’t require a mayor redesign of the features or systems (alongside updates and new small features), and leave those for the bigger updates.
Once you have more data and bugs reported you can see the bigger picture and know how to address those problems with a better design in mind. This is the same with big new content or features.
I’d say is better this way. If you try to fix problems like this one on the spot, you’ll end up rewriting core parts of your system very often, not letting it get stable, and overall, developing the software very slowly.
Hope the point I’m trying to make is more clear now.
Cheers