New ask Hacker News story: Ask HN: Who Is Jamstack Aimed At?
Ask HN: Who Is Jamstack Aimed At?
2 by aosaigh | 1 comments on Hacker News.
I've recently taken on my first project that's fully "Jamstack" [1] and I'm finding it very hard to understand who exactly these statically generated sites builders are aimed at? The project is using Gatsby Cloud and Contentful. The key problems they have encountered are a) build times being painfully slow (+5 minutes per content change) and therefore b) the authoring/publishing experience is really poor as you can't easily see previews. These seem to be common complaints of static site generators (I'm also skipping over the general complexity required to get a website up and running with so many moving parts) In order to tackle this problem, Gatsby offers a rendering feature called "DSG" (Deferred Static Generation) [2]. When enabled, instead of building all of your content up-front (the entire point of a statically generated site), only your core pages are generated at build-time. The rest of your "long tail" pages are only generated when someone first access them. To use this feature, you need to put a server in-front of your static site. What?! It seems that the build times with statically generated sites have gotten so bad that the work-around is to literally go full-circle and re-create a dynamic website. The two big benefits of statically generated sites are apparently performance and server-less infrastructure, yet to deal with the downsides of generating pages up-front you need to introduce ... dynamically generated pages ... via a server. I don't understand who this is for? Any company that requires the touted performance gains that statically generated sites offer will surely also need quick builds and a good authoring experience? But to get those build times down you have to re-introduce infrastructure and dynamically generated pages? Are there teams out there that are happy with their statically generated sites? Am I going mad? [1] https://jamstack.org/ [2] https://ift.tt/2vbCyMD
2 by aosaigh | 1 comments on Hacker News.
I've recently taken on my first project that's fully "Jamstack" [1] and I'm finding it very hard to understand who exactly these statically generated sites builders are aimed at? The project is using Gatsby Cloud and Contentful. The key problems they have encountered are a) build times being painfully slow (+5 minutes per content change) and therefore b) the authoring/publishing experience is really poor as you can't easily see previews. These seem to be common complaints of static site generators (I'm also skipping over the general complexity required to get a website up and running with so many moving parts) In order to tackle this problem, Gatsby offers a rendering feature called "DSG" (Deferred Static Generation) [2]. When enabled, instead of building all of your content up-front (the entire point of a statically generated site), only your core pages are generated at build-time. The rest of your "long tail" pages are only generated when someone first access them. To use this feature, you need to put a server in-front of your static site. What?! It seems that the build times with statically generated sites have gotten so bad that the work-around is to literally go full-circle and re-create a dynamic website. The two big benefits of statically generated sites are apparently performance and server-less infrastructure, yet to deal with the downsides of generating pages up-front you need to introduce ... dynamically generated pages ... via a server. I don't understand who this is for? Any company that requires the touted performance gains that statically generated sites offer will surely also need quick builds and a good authoring experience? But to get those build times down you have to re-introduce infrastructure and dynamically generated pages? Are there teams out there that are happy with their statically generated sites? Am I going mad? [1] https://jamstack.org/ [2] https://ift.tt/2vbCyMD
Comments
Post a Comment