because setting up a static site updating it once in a blue moon then remembering the commands to do so a second time in a few months time is less reliable than logging into a platform that isn't wordpress.com!
> Can you imagine running the same WordPress version for 25 years?
If you keep active on your Wordpress install, the regular updates will be no issue for you and will (almost) never break your website. Not sure why you would expect a regular Wordpress user to run the initial install without recommended/mandatory upgrades over a long period of time.
"Hosted blog" here means someone else is maintaining it -- Wordpress.com or some other provider. You pay a little bit of extra cash, and you don't have to spend hours deploying patches.
> It may not be very hard to maintain, but you still have to maintain it.
When the maintenance is "ensure auto updates are on, and don't do anything that would not get updated automatically" it's not like it requires regular effort.
> Whereas if you just have a collection of articles that you want to keep around as an archive, if you convert them to a static site, you can basically forget about them afterward...
Your web server, your operating system, etc. still require at bare minimum the same level of maintenance.
You can outsource that maintenance to someone else of course, but you can do the same with WP as well.
--
My point is that WP alone doesn't massively increase the maintenance burden, it's what people tend to do with (to?) WP that increases the burden and eventually leads to unmaintained sites.
Wait, what's wrong with Wordpress's update mechanism? I've only used it for a short while but I've been nothing short of amazed how simple and easy it is (two button presses), compared to years of downloading packages, diffing files, uploading files, running database upload scripts, fixing errors, and so on under phpBB/IPB/MediaWiki.
> This entire upgrade utilizes the new WordPress rest API and the new WordPress.com is open source.
To clarify: this uses the WordPress.com REST API, which has been around for a number of years, not the core REST API being integrated into WordPress (the software). Also, not all of WordPress.com is open source (i.e. you can't just clone down WP.com and run it), just the new interface. :)
They could be referencing wordpress.com, which is the hosted version of WordPress, rather than wordpress.org which is the open-source self-hosted version.
reply