5. Nobody is admitting to doing rewrites from scratch anymore.
6. Netscape/Mozilla became (due to path-dependence and happenstance) the canonical example, and no other examples have been interesting/memetic enough to displace it.
7. People have learned to keep failing rewrites dragging along until something else causes them to be abandoned, sparing them the label of "failed".
8. Other.
Most software is services oriented, and it evolves, piece by piece over time.
Is Facebook running any of the same code from 18 years ago?
Probably not?
When did they re-write? They didn't, they just evolved, piece by piece.
This claim would be more compelling if it provided a few notable examples.
Google is replacing its internal systems all the time. For example, MapReduce was replaced with Cloud Dataflow [0].
[0] https://www.datacenterknowledge.com/archives/2014/06/25/goog...
This included migrating about 1/2 petabyte of old data and rebuilding several Kimball-style Data Marts to Data Vault approach, which pairs really well with the Lakehouse-style tech stack.
This all took about 9 months, which is a long time, but it was in highly regulated industry where compliance, security and data integrity get a lot of scrutiny.
In the end, nothing of the previous solution survived - no code and no infrastructure.
1. Nobody is doing rewrites from scratch anymore. That's just not the case.
2. Nobody is talking about all the failing rewrites causing entire companies to collapse. I don't think anyone is convinced by this argument, it's basically several big conspiracies in one.
3. People have learned how to avoid the same traps, by reading about the Netscape/Mozilla fuck-up.
Basically, the problem isn't rewrites. It's badly managed rewrites.