Moderator
James Huff
(@macmanx)
Volunteer Moderator
WordPress 3.6 introduced new auto-save functionality based on browser storage: https://wordpress.org/news/2013/08/oscar/
The feature was designed so you won’t lose all of your hard work if you suddenly lose your internet connection or your computer crashes.
To disable that, use a plugin like https://wordpress.org/plugins/wp-auto-save-management/ or https://wordpress.org/plugins/auto-save-off/
Problem with this is that we are told to have as few plugins as possible and THEN we are told to add a plugin just so we can turn the autosave off!!
Why does this have to be done via a plugin? Why isn’t there just a default setting that can be turned off?
Moderator
James Huff
(@macmanx)
Volunteer Moderator
It’s one of the development philosophies:
Decisions, not Options
When making decisions these are the users we consider first. A great example of this consideration is software options. Every time you give a user an option, you are asking them to make a decision. When a user doesn’t care or understand the option this ultimately leads to frustration. As developers we sometimes feel that providing options for everything is a good thing, you can never have too many choices, right? Ultimately these choices end up being technical ones, choices that the average end user has no interest in. It’s our duty as developers to make smart design decisions and avoid putting the weight of technical choices on our end users.
Plus, if every tiny thing had a setting, it would probably take a few days to setup a WordPress site. 😉
This is why plugins set WordPress apart from the rest early on, and why there are currently 48,490 free plugins in the official directory. If you don’t find an option for something in WordPress, you can pretty much always find a plugin for it.
-
This reply was modified 6 years, 8 months ago by
James Huff.