[redbar0n]

> I forever wonder when the technical naked short options[0] will get called, but they never have in a serious way.

What does «called» mean in this analogy? That the subsystem doesn’t go away?

So your experience is that: Stuff tends to stick around? That’s my experience. I have never encountered a throw-away MVP that was actually thrown away if the product continued in the same direction (and didn’t pivot).

[thyrsus]

In the analogy to the naked short, the option is "called" when the known deficiency causes catastrophic consequences. Example: The file system is so large it takes 60 days for the backup to finish, and thus the "call" would be a multiple drive failure requiring a full restore. Example: NFSv3 with "system" security, i.e., whatever the client says it's uid and gids are, we accept that, and thus the "call" would be a malicious client declaring arbitrary unauthenticated uid/gids. See, e.g., possible publicity stunt for the movie "hackers". These are naked shorts because there are no plans to fix them.

[giantg2]

How long have you stuck around at a company? Maybe your company or business type is different, but I have certainly seen apps get rewritten or replaced over the course of 10 years. Some are built solely for some migration period. Some have been redesigned as part of a different system after a few years. Some major systems get rewritten after the continuous addition of integrations over 10 years demands a better architecture.