News for hackers. Stuff that matters.

A comment on The complicated futility of WordPress. Parent comment

Re:The complicated futility of WordPress by gwern on Tuesday February 01, 2022 @10:54PM (#30173487)
Yes, after 18 years of WordPress development, the architects' excuse of blaming bad actors in plugin ecosystem has begun to wear thin, especially when contemporaries or predecessors like Firefox or Debian never had remotely the same level of problems with their users being hacked constantly by plugins/packages.
[ Parent | on HN ]
Re:The complicated futility of WordPress by JimDabell on Wednesday February 02, 2022 @12:17AM (#30174023)
“No Way To Prevent This,” Says Only CMS Where This Regularly Happens
[ Parent | on HN ]
Re:The complicated futility of WordPress by lmm on Wednesday February 02, 2022 @02:44AM (#30174868)
Firefox has had the converse problem of constantly breaking all their plugins by changing their APIs etc..
[ Parent | on HN ]
Re:The complicated futility of WordPress by kmeisthax on Wednesday February 02, 2022 @11:51AM (#30180104)
They were able to fix this by moving to the WebExtension model instead of letting extensions directly interface with XUL/XPCOM[0]. Of course, then everyone got angry that they couldn't do ridiculously invasive changes to the browser with an extension anymore.

[0] which were then massively refactored, twice.

[ Parent | on HN ]