This is a larger ArchiveTeam problem, not a language problem. They use MediaWiki (Wikipedia) to effectively host static informational pages without a cache in front.
As the main sysadmin for the archive team's web frontend (this one happens to be hosted outside of my control) Yes, its mediawiki, no we cannot use fancy cache, JScott has a special deal with the web hoster that makes the hosting damn near bullet proof. on top of that, the overall group is anti-cloudflare. so we are kinda stuck with what Ive been able to meek out of a cpanel shared hosting plan.
Oh it doesn't work like that. I direct you to the time he got sued for 1 billion dollars. These are "crackpots" that love to threaten our services. He gets crazy as shit takedown notices about once a week. that he promptly ignores
Oh it doesn't work like that. I direct you to the time he got sued for 1 billion dollars. These are "crackpots" that love to threaten our services. He gets crazy as shit takedown notices about once a week. that he promptly ignores
Indeed. I hate PHP as much as the next dev, but Varnish and the like have been around for ages, and are easy to setup and operate. Dead simple, affordable solution for an essentially static site like this.
Tbf, the expected audience is small, its not like they are trying to sell something so its critical to stay up through some spike.
The architecture is totally fine for their use case. Arcitecturing it to stand up to hn hug of death would be over-engineering and not really make sense given their goals.