4 ms·
Meta Commentary: that people are still serving blogs out of a database boggles my mind (as I write this the blog is down because of database issues).
by bigdubs 11y ago
Meta Commentary: that people are still serving blogs out of a database boggles my mind (as I write this the blog is down because of database issues).
- nostrademons 11y agoWhat's the alternative? The blog (according to the HTML source) is pretty stock WordPress, which is database-backed.
- AlexeyBrin 11y agoUse a cache plugin or migrate to a static site (works really well for blogs).
- K0nserv 11y agoJust a regular github.io page, or if you wanna be a bit more fancy https://hugotunius.se/2016/01/10/the-one-cent-blog.html https://hugotunius.se/2016/01/10/the-one-cent-blog.html.
- nostrademons 11y agoThere's a pretty massive difference in the amount of effort needed to publish a post with either of those approaches vs. just typing it into the WYSIWYG editor on WordPress. If your time is worth $60/hour then you're looking at around ~$10/post in additional time spent. You also lose a bunch of features: comments, trackbacks, RSS, etc.
- K0nserv 11y agoGit commit and push takes a minute or two tops I fail to see how that is less efficient than clicking save in a WYIWYG editor. The setup time between the two options is probably very similar.
- BjoernKW 11y agoWhy wouldn't you? Most websites run on some sort of database. Technology can fail, especially when facing a higher load than expected but generally relational databases are among the most mature technologies in computing. Removing technical dependencies to avoid such problems is throwing the baby out with the bathwater. Besides, WordPress is dead simple to set up on almost any shared hosting plan. The static blogging solutions you probably have in mind for the most part aren't.
- bigdubs 11y agoA static compiled blog system like Jekyll, or a simple caching system in-front of the blog.