i like the boldness of their approach here. you don't NEED an SSG if you do caching right. the trick is to do caching right. Netlify bets against it, MJ and Ryan are betting for it.
SSGs just say treat caching/data-invalidation as a build-time concern (like code changes) not as a run-time concern as then you're not dealing w/ bugs w/ caching in a production environment. It's safer and easier to update your data cache through a build process. This of course doesn't always scale but for small to medium sites it's very nice.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
i like the boldness of their approach here. you don't NEED an SSG if you do caching right. the trick is to do caching right. Netlify bets against it, MJ and Ryan are betting for it.
Yeah I've been thinking more and more about this, but I think you've summed it up really well here.
Zoom back a bit and it's all just caching :-D
SSGs just say treat caching/data-invalidation as a build-time concern (like code changes) not as a run-time concern as then you're not dealing w/ bugs w/ caching in a production environment. It's safer and easier to update your data cache through a build process. This of course doesn't always scale but for small to medium sites it's very nice.