Static Hoisting
rauchg.com
rauchg.com
"Static Hoisting" is pushing data to the edge and replicating it ahead of time. Legacy CDNs are just in time. The approach discussed in this article has a performance and availability advantage.
Isn't React itself already a giant JS framework? They've made a framework-for-a-framework?
So the idea is to let developers write as though it's all one big React SPA (single page app) but then actually the static bits of it get compiled into vanilla HTML/CSS and served from a CDN?
For larger React projects, it's impractical to use the same rendering strategy for every page. Your marketing page can be static and your dashboard can be client-side rendered.
I grew up making websites using server side includes[1] and using tools like (Macromedia) Dreamweaver to generate static sties. I guess I should've just stuck with that approach but shoved the results on a CDN?
I just so feel like it can't be that obvious. Please someone learn me for my benefit.
Is this another Heroku "routing mesh" gate in the making?
https://techcrunch.com/2013/02/14/heroku-admits-to-performan...
[1]: https://github.com/zeit/next.js/discussions/11552
[2]: https://www.gatsbyjs.org/blog/2020-04-22-announcing-incremental-builds/I'm also not getting what the magic is. That little what Jamstack can actually do, might just not need a CDN?
Look at the comments here, people are more confused about this idea and terminology than anything else.