Comment It depends. (Score 2) 18
Why Auto-update is a trap.
If you have WP plugins from teams you can rely on that have a professional software pipeline serving the updates, then auto-update really isn't a problem. The key point here being of course "professional software pipeline". The broader WP community and it's huge 3rd-party market is a crazy bunch delivering the most ghetto-type sh*t in code under the sun. Quite a few of these guys shouldn't be let near a keyboard, that's for sure.
Likewise, if you've bloated your WP setup with 15+ plugins, half of which are in maintenance delay or offered up by the aforementioned ghetto faction of "developers" (emphasis on the quotes), you shouldn't be running that setup at all, either with or without auto-update.
The key problem is that WP these days is basically not a CMS but an platform and millions of users use it as a playground for their web-projects while barely knowing what they are doing. That's a huge upside since it does enable total n00bs and ords to dive deep into FOSS and FOSS-driven user empowerment - by and large actually a good thing - but with the downside being that most WP setups quickly get bloated beyond repair and eventually fail the most basic of security and stability standards.
As someone who has done a decade of WP development and using it as a key platform I don't really mind if this sort of thing keeps me in a job with things to do. What is frustrating is that you constantly have to convene with deciders would can't tell the difference between a client and a server.
A well implemented and managed WP-centric pipeline with disaster recovery in place however is a god-send when it comes to rapid development and pivoting some web-project on a dime within half an hour because some agency type person can't make up their mind about what they want. Truth be told, for most end-customer web projects time-to-market with WP is unbeatable.