WordPress is a massive shitshow, long may it rot in hell.
Right tool for the right job.
If you're trying to use WordPress to create the next facebook, you're going to have a bad time. Using it to create a fast CDN-fronted content-driven site that can easily be maintained by front desk staff? WordPress is your huckleberry.
JS-driven solutions are well suited to web apps that are complex and interactive; server-side content generation with simple client-facing markup are well suited to content delivery and content that needs to be readily seen by search engines. Getting Angular(.JS) to play well with Google is an exercise in frustration (possible, mind, but frustrating).
The above describes everything wrong with the browser frontend landscape today. The trendsetters are incredibly busy always running after whatever new framework strikes their fancy, while here I am, still having to maintain sites written in AngularJS. And I feel very lucky, because at least the (insanely) slow migration to Angular is an option. The disconnect feels astonishing.
This point is a crucial one in technology selection. It seems the younger folks often miss the "will we be able to support this application for the next 10 years with minimal budget from above?" question in the decision tree for using NewShinyJS. Maybe if every dev coming out the door had to spend a year fixing the county's COBOL database before they're let into the wild, they'd understand how long real-world production systems tend to remain in place, and pick seasoned and reliable technologies to suit the job.
At my former job, the webdevs considered the 4-year-old front-end Angular code base becoming "legacy" and in need of a (React) rewrite, while us poor backend debs had to contend with a ten-year-old* Java codebase, the only truly "legacy" bits were support for features that had been dropped years back but the code kept for that one other bit of code that kinda sorta used it.
* yes, yes, you have your 30-year-old COBOL codebases, I know...
I really don’t think the premise that WordPress market share is going to be eaten by JAM stack in any meaningful way is backed up by any of this.
WP is a dependable solution for non-tech friendly CMS whereas JAM is for broader use cases. I don't think pitting them against each other is useful.
Anecdotally I agree with the findings - many apps suit serverless + Typescript. One aspect not covered is that as these applications grow into progressively more serverlesss microservices, they become more difficult to manage as a whole application landscape. That suits very distributed teams but for a maturing company that wants a handle on its whole application estate, it can be difficult to nail down.
Biting the hand that feeds IT © 1998–2022