3 ms·

If everything is cached, sure, serving static content is cheap. The comparison with a solid machine I find it funny, a bad update in a plug-in can render your s

• Karunamon 11y ago
  An argument to be made is that it's security record is due strictly to its popularity. Given the choice between the 1000 pound gorilla that everyone uses and has double digit CVEs released every year, and the unknown that nobody uses, I'm going to pick the first one simply because the second one likely has just as many holes - there's just not enough people trying to attack it.
  • caseysoftware 11y ago
    And there are enough users - both well-informed and not - that when a vulnerability is discovered, it's more likely to be fixed and deployed quickly.
• thaumaturgy 11y ago
  Wordpress has improved a lot since version 3, and most of the vulnerabilities you see for it now require some kind of privilege escalation or don't really give the attacker a whole lot to work with (http://www.cvedetails.com/vulnerability-list/vendor_id-2337/product_id-4096/ http://www.cvedetails.com/vulnerability-list/vendor_id-2337/...). And Wordpress handles updates remarkably well, including automatically installing security updates in the background. I previously hated Wordpress because it was a source of so much trouble on the web, but now I sort of grudgingly appreciate it. I still don't enjoy having to work with it on occasion for clients, but it doesn't make me grind my teeth anymore.