3 ms·
this is actually a pretty cogent argument. how do you apply this logic to other systems and software? for example, we know that running an old version of OSX i
by arrowroot 13y ago
this is actually a pretty cogent argument. how do you apply this logic to other systems and software?
for example, we know that running an old version of OSX is not too bad. But if you're still running 10.4 instead of 10.4.3, you're in for some trouble.
when there is a security patch to a specifc X.Y release OSX or Windows, (like X.Y.Z) it's not secure to leave that running. the same would apply to any other piece of software (like WordPress), no?
- smacktoward 13y agoPretty much, yeah. Any software that is exposed to the public Internet needs to be kept up to date. If it's not, it's not secure. That means either someone has to update it, or it has to update itself. The world has been moving slowly away from manual updates to automated ones for some time now. Windows Update used to be much more oriented towards manually reviewing and applying updates than it is today. Chrome famously updates itself completely silently, and Firefox is moving in that direction. Consumer-oriented products are all headed that way, because it's the only way to keep them secure when their "administrator" is a non-technical user. WP is kind of unique in that it's a type of software (a content management system) that usually is only installed and administered by people with some technical experience, but the ease of installing WP has attracted a huge number of people without that experience to use it. So my argument would be that as WordPress has essentially become a consumer product, it should behave like one.