> but if you're used to Wordpress plugins or an NPM package being available for whatever you need, Drupal can be frustrating.
On the other hand, Drupal does not have the WordPress ecosystem habits where many modules/plugins have paid upgrades and/or scatter ads all over your site. The WP plugin ecosystem feels so scummy in comparison.
I agree the switch to Drupal 8 really killed its momentum though. (Drupal was reimplemented on top of Symfony and all existing modules/plugins had to be almost entirely rewritten to work with it - which was quite a difficult hurdle for people used to the previous conventions. Also being able to implement a site's configuration entirely in code, a beautiful feature of D7 albeit one that required third-party modules to implement, was still not quite working properly last time I checked.)
Configuration as code is actually one of the best parts of Drupal now. I think it's probably symfony as well under the hood, but you can just import / export your config with a CLI and commit as yml, makes moving configuration to higher / lower environments so pleasant.
But yes, I think with Drupal 7 there were a lot more "site builders" using Drupal, where D8 I imagine it's mostly just developers left standing.
On the other hand, Drupal does not have the WordPress ecosystem habits where many modules/plugins have paid upgrades and/or scatter ads all over your site. The WP plugin ecosystem feels so scummy in comparison.
I agree the switch to Drupal 8 really killed its momentum though. (Drupal was reimplemented on top of Symfony and all existing modules/plugins had to be almost entirely rewritten to work with it - which was quite a difficult hurdle for people used to the previous conventions. Also being able to implement a site's configuration entirely in code, a beautiful feature of D7 albeit one that required third-party modules to implement, was still not quite working properly last time I checked.)