[roel_v]

"is that the author arrives on the two node-based solutions as the preferred path forward."

That's the generous interpretation. A more jaded reader might have started reading the article thinking 'mention of Angular... 3... 2... 1... ah there it is! suggesting node... 3... 2... 1... ah there it is! Well at least he managed to contain himself until the next to last paragraph'.

It's technology-centered myopic navel-gazing. Yeah nobody uses Wordpress because PHP in templates is not 'clean'... Oh wait, half the world does use Wordpress because everybody and their dog has a server with PHP and because it's dead simple to hack up something working by cramming some PHP into a template you bought for 5$. For 95% of all websites, who cares about maintenance? Just do a new one in 3 years with whatever is hot then.

This article (and many like it, not singling this one out) reads like people who call themselves 'real' woodworkers, lamenting that people won't fork over $2500 for a hand-crafted oak dining table and instead get a $100 Ikea one. The popularity of 'Ikea hacks' amongst the crowd that tends to author articles like this is ironic in that sense...

[geon]

Have you ever tried to modify a wordpress theme? It's a nightmare. And we are proffessional developers. Imagine the pain this must be for mere webdsigners.

Fixing the mess that is wordpress is a very nobel goal.

[pmlnr]

Write your own and keep it simple. It's not that hard.

The ones you can buy however are a nightmare for sure, so are most of the copy-pasted-glued-together ones.

[geon]

Admittedly, it was a few years since I looked at the inside of wp, but it was horrible, with php api calls inside the template code, bad/missing/misleading documentation and non-existing database structure.

[lhorie]

I have, and I somewhat disagree. I agree that it can feel dirty to your programmer sensibilities when you start from the base template one and go "building from the ground up", but if you set expectations accurately with the client (and yourself) wrt the amount of flexibility a theme gives and what type of work you're going to be doing, you can get some pretty high quality themes (where "quality" here refers to the template's ability to fulfill the goal of offering a feature-rich GUI to non-techies). Some themes are so elaborate that you can change virtually every aspect of the template down to the most granular levels directly from the admin interface.

And where wordpress really shines is in the ecosystem. Subscription list popups, SEO, social media integration etc are just a few things that clients commonly want that take far less time to integrate into wordpress than building from scratch (because it's fairly common that authors of less popular developer-centric CMS'es didn't think to implement those things).

[weego]

Come on, nightmare? It's kinda annoying, fussy and handle-turning, but taking a page that has been designed and fitting that into the template tags is really not all that bad for a days work.

[geon]

I had to clone a website, then make a few tiny adjustments (like change the site name), and it took me several days.

[ninjaboy]

> Have you ever tried to modify ikea furniture? It's a nightmare. And we are professional carpenters. Imagine the pain this must be for mere hobbyists.

[geon]

Bad analogy. My brother (who is a non-carpenter web designer) shortened an IKEA bed recently. Apparently it wasn't a big deal.

[jyaker]

> And we are proffessional developers

In my experience, WordPress is not built for developers or designers. It's built to be simple and extensible from the end-user's point of view. Most end-users don't expect absolute perfection and accept that it will do 90% of what they want. As long as it keeps doing that, no one will care what a "mess" the insides of it are.

[geon]

> no one will care what a "mess" the insides of it are.

...except the poor bastard who will have to build the website and maintain it.