News for hackers. Stuff that matters.

A comment on WordPress 18. Parent comment

Re:WordPress 18 by nr2x on Friday May 28, 2021 @08:29AM (#27314569)
From an engineering perspective it is absolute garbage. There is practically no separation between View and controller layers, which is a big part of the reason otherwise simple cosmetic plugins are security and stability vectors.
[ Parent | on HN ]
Re:WordPress 18 by b0ner_t0ner on Friday May 28, 2021 @09:15AM (#27314958)
That's why a whole dev ecosystem on a modern stack exists: https://roots.io/
[ Parent | on HN ]
Re:WordPress 18 by nr2x on Friday May 28, 2021 @09:27AM (#27315072)
At that point why not just make something properly designed to start with?

At the end of the day, regardless of other usability and adoption merits, it’s just a really poorly designed architecture.

[ Parent | on HN ]
Re:WordPress 18 by b0ner_t0ner on Friday May 28, 2021 @10:49PM (#27322665)
> At that point why not just make something properly designed to start with?

Of course that would be ideal development-wise. Business-wise, I doubt most agencies or small teams are going to rewrite W3 Total Cache, Yoast, WooCommerce, Elementor, ACF, Gravity Forms and all the top popular plugins... not to mention all the battle-tested security options.

[ Parent | on HN ]
Re:WordPress 18 by nr2x on Saturday May 29, 2021 @04:07PM (#27327894)
This is classic sunken cost fallacy, the reason to stick with a platform shouldn't be it has the most bandaids covering deep, deep, problems and all the investment that has gone into bandaids can't be given up.
[ Parent | on HN ]