I guess the missing brace is a scope delimiter and easy to notice if missing, while the tab is an indentation marker and much harder to spot, and might get you into an invalid state but still parse correctly, just not doing what it was meant to do
Unless I'm misunderstanding your point, your HTTP server from 35 years ago is still working today without any maintenance?
Does that mean no security patching and no updates for bugfixes? or does "no maintenance" means something else I'm missing?
I find it difficult to discuss these topics when comments like these pretend that you can leave your system exposed on the internet for years without any maintenance.
If we're talking applications that don't actively listen on the internet that's fine, and I would agree that we should have complete software that just works.
But a webserver, unless it's for personal/home use, it's on the internet and I don't see how it could work for 35 years without any update/change
This story is super interesting and I think can teach us some valuable lessons about refactoring and the price of truly understanding the domain in which the code operates.
The accompanying article is also a pleasant reading with a nice bit of background, and I really liked the motivation behind "layering" on top instead of rewriting from scratch.
Most likely you know already, and if that's the case just ignore this comment please. Spawn camp in this context is referred to gaming terminology where it indicates an enemy that camps/waits for for a long time and kills you as soon as you are put in the battlefield, which is your spawn point, hence spawn camping