Well, I can say, as a person who's been running a blog since 2003 or so, if you're planning a long-running online presence, building a site based on technology

Well, I can say, as a person who's been running a blog since 2003 or so, if you're planning a long-running online presence, building a site based on technology that makes it relatively easy to move to different technology platforms is really important. a) it future-proofs your site so you can move as the technology moves, but also, b) the odds are you'll end up with content that's easier to back up, manipulate, etc. The first iteration of my blog was based on an old wiki engine, and the beauty of that engine was that, while the markup format was unique, the data was stored in flat text files that I could easily manipulate. Some number of years back, now, I moved to a static site generator that uses Markdown as the source format, and since I was dealing with flat files, I actually had a fighting chance of making the switch fairly easily. And now that everything is just Markdown, I can version control it with git, back it up easily, etc. And again, if I decide to switch technologies in the future, I can do that because the content is stored in a format that's very easy to manipulate. And thinking very long-term, this kind of approach ensures that archiving your digital legacy will be a lot easier, since the content isn't tightly bound to a specific technology.