However. While Next.js, Remix, and friends continue to thrive on midsize, dynamic websites (think Notion, think Twitch, think Hulu), they also continue to be the gold standard for e.g. blogs (as Zach points out, the three biggest JS-based frameworks all feature blogs on their tutorials). And for a blog, it feels like web developers—and more importantly, their users!—are being underserved.
Note here that I'm only kind of talking about static site generators. There are tons of frameworks that turn source files into plain HTML, and a lot of them (like Zach's Eleventy, or Jekyll, or Hugo) are very good!
These frameworks are pretty good at turning Markdown files into web pages (even if, as I say, you're subscribing to years of complicated dependency update headaches). And they're even getting good at playing nice with the browser: the correct HTTP status codes, route change announcements for accessibility tools, that sorta thing. And that would be a big deal—if that hadn't been table stakes for boring web technologies for almost 20 years now. If you're just building a blog, you can get up & running with WordPress in minutes—and I promise that your users won't notice the difference between a relatively stock WP installation (+ optional Cloudflare) and your edge-delivered incremental-static-generated Next site. And deployments will be a lot quicker, too.