3 ms·
Yes, this is my point exactly. Except much more succinctly stated :-D In WP's defense, though, it is not the only blog/CMS product that works this way -- the v
by smacktoward 14y ago
Yes, this is my point exactly. Except much more succinctly stated :-D
In WP's defense, though, it is not the only blog/CMS product that works this way -- the vast majority I've used require some kind of user or admin interaction to apply updates, mostly to avoid people complaining if an update should break something. And WP's update process is much easier and friendlier to non-technical users than most are.
But in practice that turns out not to matter much, because no matter how easy making that intervention is, some percentage of users are going to skip it. The only way to get around that is to not require the interaction at all. That may risk breaking some stuff, but I'd rather work in an ecosystem where everybody's secure and poorly written extensions break occasionally than one in which poorly written extensions never break at the cost of security.