Literally modern frontend frameworks that don't want to do SSR.

Is it that surprising?

The only useful content on the page was not only static text, but static plain text.

If the modern frontend framework can't display that without JS, then I think it's fair to call it a shitty frontend framework.

More so it's not configured to do that - which depends on the priority of the team working on it.

Well that's true for anything, so it means nothing. I know someone who was told with a straight face, in a meeting about an out of control memory leak in some software, "not leaking memory wasn't in the requirements."

LOL! That must have been some poker face! Unbelievable!

I mean, they're not wrong, but I've handled that stupidity by making sure my next requirements included "Do not have sexual intercourse with your coworkers" and "Be a professional software engineer"

Edit: It's kinda like the story of the guy on the ship who was forced to write accurate logs and wrote "The captain was not drunk today"

And leaking memory is actually a valid tactic when you're writing software for financial systems that have scheduled times to turn off.

In various HFTFs GC is completely disabled since that valuable cpu time is useful for other things.