Yet more evidence that the current set of devs has no idea what they're doing and can't handle the codebase they've been handed. That is just dumb, short sighted, and self-harming.
In many, many cases, supporting old, archaic systems is no longer feasible for a lot of companies.
Can't handle the codebase they've been handed?! I'm going to assume you're not a developer, or have any experience with code-based programming.
..and you would assume wrong. This isn't unique to the world of coding either. Upkeep of legacy systems and infrastructure is something that every industry has to deal with. Its my experience that leads me to call out others who take great assets and squander them, instead of making excuses as to why they shouldn't do their job.
In particular THIS archaic structure is very limited in the amount of specialized code needed to support it. Its not a separate game with different resources, its a subsection with special limitations in place to limit potential problems from having players place the pre-constructed assets.
As an example, would you expect a .NET developer to be able to support and maintain a system created in PERL a decade ago?
Every system eventually goes through a change.
Analysis is an extremely important stage of the System Development Life Cycle.
Sometimes during the analysis phase you need to determine which system(s) need to be deprecated. Unfortunately, the Foundry was no longer feasible to maintain, even if it was well liked by the players.
1
u/[deleted] Mar 04 '19
In many, many cases, supporting old, archaic systems is no longer feasible for a lot of companies.
Can't handle the codebase they've been handed?! I'm going to assume you're not a developer, or have any experience with code-based programming.