3 ms·
Looks nice. If we're going to compile our FE code (sometimes once with production babel/webpack builds, sometimes more often with every server-side rendered c
by wildermuthn 9y ago
Looks nice.
If we're going to compile our FE code (sometimes once with production babel/webpack builds, sometimes more often with every server-side rendered cache miss), then we might as well go all in with static-site generators. The epitome of this trend is https://www.gatsbyjs.org/ https://www.gatsbyjs.org/, a framework designed around GraphQL and React.
- fiatjaf 9y agoIn more-or-less the same niche as Gatsby there is my Sitio[1], which also uses React (so kinda isomorphic pages), main differences being: - No GraphQL stuff, but instead you'll use imperative JS code to tell the library which pages you want to build, with data from anywhere (files, CMSs, hosted contents elsewhere etc.) you can fetch using the same JS code, transform with any library etc. - No Webpack, no Webpack transforms. I suffered when I tried to use Gatsby because of the gigantic dependencies on Webpack. I guess it's changed nowadays, but still I'm hurt and won't go back there. Here we're proud to use Browserify and go with more modular architecture. [1]: https://github.com/fiatjaf/sitio https://github.com/fiatjaf/sitio