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

Static html webservers don't really have any need for security patching or bugfixes constantly like dynamic complex stuff. They literally can just live forever. The sites themselves are just files. Not applications.

I hate to break it to you, but HTTP servers (what is an html server) absolutely can have all manner of fun exploits, like RCE.

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.

Thanks for bringing this story to HN!

I referenced a LOT of articles and case studies on legacy rewrites and ports in that first year. It is definitely a challenge that even with LLM still exists and I am happy to add to the body of knowledge surrounding the subject.

Not relevant to the language itself but to the grammar: https://languagelog.ldc.upenn.edu/nll/?p=73

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

Thanks, I had not understood previously, and was parsing the sentence incorrectly. I have no prior knowledge of the dangers of honey.

Merry christmas and thanks for being such an awesome community

Even with substantial differences, I believe that the principle of <Contra proferentem: "Against the offerer"> described in section 8.4.2 of "Notes on Contract Drafting" (https://toedtclassnotes.site44.com/Notes-on-Contract-Draftin...) also offers a similar level of protection against unexpectedly ambiguous claims.

Felice anno nuovo! Have a wonderful new year you all, hope things will be going great for you and you will experience great joys and many unforgettable moments!

Merry Christmas to everyone!

Sorry for the OT, what is "TFA"?

Sorry. The Fine Article. I didn't mean it in the disparaging connotation.

It's a reference to RTFM, Read The Fine Manual.

TIL: RTFM was a phrase from the 40s : "Read the field manual."

I never seen the F in RTFM mean “fine” before. I’ve always seen it used as the more vulgar “read the f*ing manual”.

I believe that's the joke.

It's the same as OP, except it only means the Post, not the Poster. (The F* Article.)

Usually it's a kind of negative retort - 'well if you'd actually bothered to read TFA then ...' - but increasingly it seems to be used without such emotion (particularly, to me anyway, on HN) to mean simply 'the submission'.

I always read it as "the featured article".

I am amazed by "Structure and Interpretation of Computer Programs". Unbelievably good on the technical side and all around a nice introduction to programming, highly recommended