2 ms·

It's the dream of the 1890s as if caching and CDNs were never invented.

swalkergibson 13y ago
For me, the site's latency is not the issue. I find myself pulling my hair out trying to make the Wordpress admin area work the way I want it to work. If I can just stay in vim, I am a happy camper. If you force me into some WYSIWYG editor inside of an admin panel, I am going to get frustrated.
- ereckers 13y ago
  I hear ya. I work in VIM and the command line all day too and for a simple blog I can see the frustration with the WYSIWYG editor. That won't fly with a marketing team of a couple inbound marketing experts though. WordPress does have a Command Line Interface and you can in fact write to a text file and import it as a new blog Post: - http://wp-cli.org/commands/post/create/ http://wp-cli.org/commands/post/create/ You can actually do a ton with it. I don't know how familiar you are with WordPress but with CLI you can upgrade WP core, update/add/activate/deactivate plugins, and much more with it: - http://wp-cli.org/ http://wp-cli.org/ It's a nice tool for WordPress developers that want to bypass going through the admin panel.
  - swalkergibson 13y ago
    I had no idea that existed! Pretty cool! Thank you for the tip. That is slick!
lambda 13y ago
People don't use static site generators to simply avoid having to set up caching. They use them for their simplicity and flexibilty. You can edit the posts anywhere, even when not connected to the net. You can use your favorite text editor to edit them. You don't need to worry about upgrading your blog engine to patch out the latest security vulnerabilities. If you later decide to change markup formats, or templating systems, or change your blog engine entirely, you don't need to decide between importing your content into the new one (which is generally a messy and lossy process) or running an outdated one which you still need to keep security updates on or being exploited; you just leave your old static files alone, and use your new generator or blog engine or whatnot for the new content. It's obviously not appropriate for every use case; if your data really needs to be dynamic, then it doesn't help. But there are plenty of reasons to use it beyond just efficiency, and even there, it makes getting those efficiency gains a lot easier than a dynamic site does.

For me, the site's latency is not the issue. I find myself pulling my hair out trying to make the Wordpress admin area work the way I want it to work. If I can just stay in vim, I am a happy camper. If you force me into some WYSIWYG editor inside of an admin panel, I am going to get frustrated.

ereckers 13y ago
I hear ya. I work in VIM and the command line all day too and for a simple blog I can see the frustration with the WYSIWYG editor. That won't fly with a marketing team of a couple inbound marketing experts though. WordPress does have a Command Line Interface and you can in fact write to a text file and import it as a new blog Post: - http://wp-cli.org/commands/post/create/ http://wp-cli.org/commands/post/create/ You can actually do a ton with it. I don't know how familiar you are with WordPress but with CLI you can upgrade WP core, update/add/activate/deactivate plugins, and much more with it: - http://wp-cli.org/ http://wp-cli.org/ It's a nice tool for WordPress developers that want to bypass going through the admin panel.
- swalkergibson 13y ago
  I had no idea that existed! Pretty cool! Thank you for the tip. That is slick!

lambda 13y ago

People don't use static site generators to simply avoid having to set up caching. They use them for their simplicity and flexibilty. You can edit the posts anywhere, even when not connected to the net. You can use your favorite text editor to edit them. You don't need to worry about upgrading your blog engine to patch out the latest security vulnerabilities. If you later decide to change markup formats, or templating systems, or change your blog engine entirely, you don't need to decide between importing your content into the new one (which is generally a messy and lossy process) or running an outdated one which you still need to keep security updates on or being exploited; you just leave your old static files alone, and use your new generator or blog engine or whatnot for the new content. It's obviously not appropriate for every use case; if your data really needs to be dynamic, then it doesn't help. But there are plenty of reasons to use it beyond just efficiency, and even there, it makes getting those efficiency gains a lot easier than a dynamic site does.