From: London, Surrey, United Kingdom
The unfortunate fact is, the more you make an old horse pull the slower it gets. If all of the planned bangles are loaded on the cart the horse may well refuse to move at all.
This is sort of nonsense. The software I deploy for a living is almost as old as TOAW and is many, many times more complex than it was back then, and handles far more data. At no time has anyone rebuilt the code base from the ground up, but it still works smoothly.
Deploying new features should not have a material effect on performance. It really doesn't make a whole lot of difference if the map reference you're entering has 90,000 different possibilities (a 300x300 map) or 490,000 (700x700). The problem is that since the move to TOAW IV, changes to the code base have been apparently been applied in an ad-hoc manner and without rigour, in order to deploy new features faster on a very limited resource.
This is understandable as Matrix is a business and they want a return on their investment, and people will only buy a new product if it has some significant enhancements over its predecessor. But it leads to a frustrating end user experience.
"What did you read at university?"
"War? Huh. What is it good for?"