3 ms·

What a strange comment. Yes, caching is intelligent and will help you scale, but there's nothing inherently wrong with dynamically generated pages. > Generatin

What a strange comment. Yes, caching is intelligent and will help you scale, but there's nothing inherently wrong with dynamically generated pages. > Generating the pages on each request is madness, and is why Wordpress in the default configuration (without WP Total Cache, which allows the httpd to bypass Wordpress entirely for most requests) falls over as soon as it's linked from any media site. No, it is not. WordPress is slow because it has an exceptionally poorly designed database schema, which requires SELECT DISTINCT and joining on the same table multiple times per query in order to do anything meaningful. > Compile your blog to static pages and deploy those. Hugo, Jekyll, and a million others await you, as well as CF Pages, S3, GitHub Pages, Netlify, and others. One downside of this is that you have wait for a compilation process every time you make content changes. Another is that any forms you might have still need a backend of some kind. Static sites are really only appropriate for sites that rarely ever change. A blog may or may not change frequently enough to warrant a backend.

sneak 3y ago
> Static sites are really only appropriate for sites that rarely ever change. A blog may or may not change frequently enough to warrant a backend. Any modern SSG can build and deploy in under a minute, usually in single digit seconds. This isn't really an issue in practice at all. Static sites work fine even if you are updating many times an hour. This is a far cry from "rarely ever change".
- evantbyrne 3y ago
  You're conflating build times and deploy times. A low friction deployment might take a couple minutes end-to-end for something that "builds" in a few seconds once the CI is booted up. Sure, that's fine for hobbyist stuff that is always being edited by the web developer and nobody else. The point is a proper backend editing experience brings so much to the table. Once upon a time, my promotion was delayed because the team lead I answered to decided to use a SSG instead of a proper CMS, and non-technical stakeholders were not happy about the limitations.

sneak 3y ago

> Static sites are really only appropriate for sites that rarely ever change. A blog may or may not change frequently enough to warrant a backend. Any modern SSG can build and deploy in under a minute, usually in single digit seconds. This isn't really an issue in practice at all. Static sites work fine even if you are updating many times an hour. This is a far cry from "rarely ever change".

evantbyrne 3y ago
You're conflating build times and deploy times. A low friction deployment might take a couple minutes end-to-end for something that "builds" in a few seconds once the CI is booted up. Sure, that's fine for hobbyist stuff that is always being edited by the web developer and nobody else. The point is a proper backend editing experience brings so much to the table. Once upon a time, my promotion was delayed because the team lead I answered to decided to use a SSG instead of a proper CMS, and non-technical stakeholders were not happy about the limitations.