In reply to Joel Newcomer.

When you have software that powers 1/4 of the Internet, it's a dangerous position as a developer to straddle.

WordPress Core seems to think WP is simply a blogging platform. They don't want to add features that make things harder for amateurs getting started or risk blowing up the DIY market.

Hardcore WP developers seem to think WP can "do it all" and want things like Advanced Custom Fields/Pods or Yoast SEO, etc. right in the Core.

I can see it from both sides. Most of my websites don't use WP anymore but it can be still relevant for the 5 pages and a blog site. Majority of my work is in client services, i.e. building websites for businesses.

On bigger installations, WordPress' simplistic nature tends to break down pretty quickly when you have more than a few content types. You can add plugins that make it more CMS-like but ultimately, we're chasing after several different plugins to provide the functionality that other CMS offer right out of the box, from one developer. It's not even close to a cohesive solution.

I don't need comments, I don't need XML-RPC, I need more than one content (post) type. And I absolutely need more than one field (body) for content editing. These are things that Core doesn't seem to want to solve at all for me. And ultimately you need plugins or custom code on every build to make it happen. That multiplies the risk/maintenance factor with every plugin you add.

Devs love to point out that huge players use WordPress and that if they can do it, WordPress has plenty of power for your SMB website as well... but neglect the fact those teams often have dozens of developers on them to actually support the installation.

Why do developers continue to use WP if it doesn't really meet their needs? I still use WP when it makes sense but in a developer/client relationship, most of the time it does not.