I can't wait for the HN comments telling you you're wrong even though it's lived experience because they want a place where they can spend their tech windfall before it's "ruined" by Americans.
Yeah, simply the playground of rich Americans instead of a piggy-bank for a corrupt government that executed political opponents and routinely jails dissidents.
Our studio, Marquee (https://www.marquee.studio), has an in-house publishing platform called Proof (https://www.proof.pub) that we started back in 2012 which couples fully customizable editorial tools and content model, a headless CMS, and React/Serverless based SDK to compile static websites specifically for editorial and content marketing teams. An example that was designed by our team and managed through Proof that HN is probably familiar with is The First Round Review (http://firstround.com/review/).
It's a similar approach that Netlify has put together and works great. Can't advocate for it strongly enough.
I think what happened is a lot of people in our cohort figured out how to use the trolling techniques honed on forums and in flamewars on the general public. You can see it reflected across the web now in ways that have caused real, lasting damage.
And while I agree that we're the first digital natives, I think what screwed the pooch was a massive influx of boomers into social networks, and everything that comes from having a bunch of non-digital natives suddenly being given tools they weren't ready to handle.
Who knew a textarea and a notification system could become so troublesome?
For content-driven websites, static sites are great regardless of editorial complexity. We (https://www.marquee.studio) build editorial tools that connect to our headless CMS (https://www.proof.pub) and compile static websites to be distributed on a CDN. Sites load quickly, and it's a much safer to have your CMS decoupled from the eventual editorial product.
Plug: Our publishing platform — https://proof.pub — combines an editorial suite, API-based CMS, and Javascript/Sass SDK for creating static compilers using server-side React. When content is released through the editorial suite, we perform a static compilation and push the resulting archive to CloudFront. Works great, sites load quickly, and it all scales very simply.
This kind of hyperbole is exactly why we have the president we do.