It amazes me that so many people find WordPress inadequate and/or intimidating even though it requires so little of the admin in order to setup while being incredibly powerful.
I've used Drupal and Joomla and I can't fathom why anyone would prefer those platforms over WordPress.
Thenagain, I've been using WP since version 1.0...so maybe I have been trained to accept a way of operating that isn't necessarily ideal. But I've never heard an argument for why WordPress sucks (asides from the source code).
I think you see a lot of negative reactions about WordPress on places like HN because hits a bitter-spot (anti sweet spot) for most web application engineers:
* You don't start interacting with it via code or text files -- you administrate it through a series of web forms.
* Customization is done through plug-ins rather than composing familiar framework abstractions
* If when you do decide to look under the hood, it's not organized like any familiar back end from the last 10 years and will take you longer than usual to figure out
* Oh, yeah, PHP
It's pretty hard to argue with its success for people who aren't webapp engineers, though. And even from the engineering standpoint, after I had spent 2-3 years working on projects that used it as a basis for a platform, I came to a grudging (if tepid) respect for it.
Comments
It amazes me that so many people find WordPress inadequate and/or intimidating even though it requires so little of the admin in order to setup while being incredibly powerful.
I've used Drupal and Joomla and I can't fathom why anyone would prefer those platforms over WordPress.
Thenagain, I've been using WP since version 1.0...so maybe I have been trained to accept a way of operating that isn't necessarily ideal. But I've never heard an argument for why WordPress sucks (asides from the source code).
I think you see a lot of negative reactions about WordPress on places like HN because hits a bitter-spot (anti sweet spot) for most web application engineers:
* You don't start interacting with it via code or text files -- you administrate it through a series of web forms. * Customization is done through plug-ins rather than composing familiar framework abstractions * If when you do decide to look under the hood, it's not organized like any familiar back end from the last 10 years and will take you longer than usual to figure out * Oh, yeah, PHP
It's pretty hard to argue with its success for people who aren't webapp engineers, though. And even from the engineering standpoint, after I had spent 2-3 years working on projects that used it as a basis for a platform, I came to a grudging (if tepid) respect for it.