This is a dangerous metaphor. Remove the old wall and it turns out the new beautiful wall was leaning against and supported by it.

I get what you mean, it’s just that the metaphor could support both perspectives.

Making the new wall is not a money generator. You would be insane if you think suits would waste money to rebuild something when it generated minimal to no additional revenue.

no one has a budget for that

your whole team is fired, we got ‘Bob’ from India handling this now

Developer, smacking wall: "This bad boy ain't going nowhere"

User base, rolling up their trebuchets:

Excellent point. For those who are unfamiliar: Survivorship bias

Well that's not true. I live in a Soviet era house that had an entire second floor built on top of it. We've had to drill through the brick walls to replace the natural gas pipes with pipes that run outside the walls, we've had to dig under the foundation when we got connected to the city's sewer system (again, Soviet-built), and again when the main water pipe burst and threatened to wash out the foundation. If the load-bearing walls had been constructed to the same "it works" standard as the things we've had to fix, we wouldn't have a house anymore.

You don't ever HAVE to update software though. That's just the way it's usually done now. It's a choice. Usually updates are made to add more features or monetization or whatever but you could just not do that.

If you look at old video games for example those were released and never updated again. They will still work today too.

My wall keeps crashing and I don't know why.

Uhm...

I've rewritten much of my code as needs changed, I call myself an idiot a lot since I've worked on this program nearly a decade and was my first professional software so often change old code I wrote. Though it was more additional at first since I used a lot of code the lead programmer did. Though he duplicated everything as needed for a tiny change ugh. Least I know how not to do it.