4 ms·
It's all about how you prioritize the problems you need to solve. At my current job we primarily use Wordpress. Why Wordpress? Because we have a large and no
by busterarm 11y ago
It's all about how you prioritize the problems you need to solve.
At my current job we primarily use Wordpress. Why Wordpress? Because we have a large and non-technical content team, 260+ websites and several tens of thousands of pages of content that need to go up quickly.
We're just 4 developers - about 1 for every 8 content & marketing people we have. We spend very little of our time on frontend. Tell me that you're going to get that kind of leverage with another tool.
Wordpress is just about the last thing that you would pick as a developer or ops person to base your tech stack, but in our case it is the right choice.
Aside: Coming from Rails and having spent six months deep in Wordpress core, it's actually kind of awesome. Seemingly every problem is solvable.
- askyourmother 11y agoWordPress is a pretty crazy codebase, yet, it seems sane compared to Rails. Interesting that WordPress as a service are moving to a node.js backend from PHP - even they chase shiny too
- busterarm 11y agoDo you know of any decent (modern stack) WPaaS besides Pantheon?
- btdiehr 11y agoIs it not an advantage for average users to be able to do both the front end and back end knowing only a single language?
- askyourmother 11y agoThe same advantage as just using a screwdriver to handle nails and screws? No. Right tool on the server (hint: it's not JS nor node), right tool on the client (JS if needs must)
- kennell 11y agoComparing Rails and Wordpress seems like apples and oranges to me. Rails is a framework that lets you build anything web-app-ish, while Wordpress has its well defined, rather limited use cases. If it works for you, great, but the scenarios are different.
- busterarm 11y agoThat's not the point of what I was saying. I'm making a point that Wordpress is also "yesterday's software" and there's nothing wrong with making that choice.