Hacker News Reader

Comment by donutdan4114 | Hacker News Reader

I would argue that Drupal's target is much different than Wordpress'. Yes, Drupal has a tiny bit of focus on small sites, but Drupal can't contend with Wordpress, not even close. Wordpress is much faster to setup and get a nice looking site up and running.

Where WP falls short is in the enterprise market, and this is where Drupal's ideal customer is. Drupal powers Tesla, Whitehouse.gov, Weather.com, Economist, NY.gov, and other major sites. So for Drupal to remain relevant to these types of clients it has had to play catchup. D7 changed a lot from it's initial release, and a lot of contrib modules helped make it a decent enterprise-level solution. But D8 is a whole new beast that really sets the bar pretty high. You can literally build anything in Drupal, and with it's new focus on having "headless" RESTful services, it can be used to power your entire content strategy (pushing content to apps, other sites, etc).

View on HN

> Wordpress is much faster to setup and get a nice looking site up and running.

I would argue that this is faster than most Wordpress setups:

    drush dl drupal
    drush si drupal ...
    drush en "name of theme"

Wordpress is easier to set up only for the "I still use tools from a decade or two ago" crowd.

I mean, I don't just mean setting up a bare site. Between setting up content types, fields, putting in content, downloading additionally needed modules (which got better in D8 with Views/Twig/CKEditor in core), and how much custom theming has to go into a Drupal site, I feel like WP is generally much faster to deal with and has more beautiful themes/widgets that you can just plug n' play. However, I'm not an expert in WP dev. But I wouldn't recommend Drupal to a very small business that needs a basic site. For that I would recommend WP, squarespace, wix, or equivalent. I would only recommend Drupal if someone needed some enhanced functionality, in which case, Drupal is a great platform.

That's presuming they can have command line access and the tools/know how to install drush. I suspect a lot of WP installs start with a single click button on a graphic UI.

Both have an easy CLI setup:

http://wp-cli.org/

There are solutions catering to SAAS/application-specific hosting for both. Wordpress.com / Drupal Gardens as well as containers and configurations scripts you can use to get a jump start.

Both have similar philosophies in the sense you can login and immediately start switching on modules/extensions you want to use. Both are CMS.

How much experience do you have using wp-cli? Drupal/drush are a long long way off perfect but comparing drush to wp-cli is apples and oranges.

wp-cli is extremely brittle even for very simple download+install, produces very poor defaults in terms of file/directory permissions and general on-filesystem stuff, and this is before you get into things like drush's many other functions for general admin or its extensibility.

That is not a criticism of wp-cli's developers though, as about 99.9% of its limitations are down to the Wordpress core team's complete disinterest in accommodating its functionality well or in providing a codebase that fits into a modern deployment setup in any reliable, well-considered way.

The work done on wp-cli is really commendable: it seems to be battling against quite a tide.

The above three drush commands get a site technically functioning, but it's typically a long way off being a "nice site" or being "up and running" in the push to production sense.

WordPress's out-of-the-box post install experience is a lot nicer and a lot closer to being a "finished" and ready site.

Reply on news.ycombinator.com