๐ถ Freeman
Just want to share my thoughts here. I've worked with react for the last 5 years. However I've started seeing a trend and it's for a good reason that people incl me realise the trade offs of reactivifying everything. Esp for a blog, a non SPA server rendered page works with less moving parts, or a html only SSG (i use zola). You could mount extra reactivity with Web Components (e.g remount). PS i still use next.js, not trying ti dismiss it :)
Matt Palmer
I hear that, though I'm very happy with the particular set of tradeoffs next.js represents. At the end of the day I enjoy writing React too much :) so it's nice to find something that will output something that statically renders what it can, and progresses pretty gracefully from there.
๐งต Evan
You can React-ify static sites too! I'm pretty sure that's what Gatsby is. @msp it's way cheaper (usually even free) to run a blog using a static site hosted on Netlify. I wish I could find an alternative to Netlify, because I feel like they're getting too big, but that's what seems to work for now.
Matt Palmer
In fact this works very much like Gatsby! I'm using Vercel, the (recently renamed) company that develops next.js. As far as I can tell their solution is free for personal sites.
๐ถ Freeman
I also ended up with netlify but at least you know you won't be vendor locked when all you host is static files :) my main beef with react based SSG is that you still ship the whole page in your js bundle (for hydration), even when your whole or most of your page is totally static. waiting for a react framework that supports partial rehydration