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 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.WordPress's out-of-the-box post install experience is a lot nicer and a lot closer to being a "finished" and ready site.
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.
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.