for some reason i occasionally ponder about highly optimized static site generators but the complexity of making sure the updates stay incremental despite humongous sites is oppressive.
then i remember *literally nobody cares* when the site gen gets too slow they just yeet the generator and go back to PHP.
then i remember *literally nobody cares* when the site gen gets too slow they just yeet the generator and go back to PHP.
Are you talking about something like squid, or generally like memcached, or are you talking about something else?
@Pat there are static site gens like nanoc and hugo which consume text files, follow a set recipe, and output a new one. they *maybe* do a tiny bit of dependency testing like if the template does not change and the article does not then they leave the files alone.
some like frozen-flask and gatsby are not so smart. they just iterate the whole database they are attached to every run.
when people asked about gatsby fixing it they just coped out about enterprise features instead.
some like frozen-flask and gatsby are not so smart. they just iterate the whole database they are attached to every run.
when people asked about gatsby fixing it they just coped out about enterprise features instead.
Follow
Ok. I just went to school to learn about SSGs. Wow you blink your eyes and you miss a whole sector of the webaverse. These things happen when you're retired. 
Without knowing anything about them, I probably would have tried to make one out of an awk script or something. (old-school)
Those things look like pretty useful creatures, though.
Thank you.
there are ways to structure your data i think so you can do incremental updates of huge sites. but nobody really puts in the effort. when the site gets too huge you just stop using the SSGs and just rely on varnish caches etc.