These things take time to sort out. Anyone moving platforms now, due to the drama, isn't going to show up in surveys/polls until after they've migrated. And depending on the size of their site, a migration could take the better part of a year. I expect we'll see how the sands are shifting by next July.
Drupal still has a very high learning curve. I'll use Drupal over WP any day, but I can acknowledge it has some rather rough edges.
I haven't dug into it yet, but I think that "starshot" initiative that's been Drupal.org's front page since the last DrupalCon might be aimed at giving people an option without the rough edges.
Personally, if Wordpress handled security alerts with plugins the way Drupal does, and if they did a better job of keeping bad code out of plugins (why can a theme implement a form?? At least that was the case years ago. Has it changed?) I'd give WP a serious look again.
Drupal peaked in like 2009. It’s mostly built by “click monkeys”, as you can do a lot by clicking around the UI to build stuff. But it’s old and even the founder abandoned it long ago around 2012.
people use it because they didn’t learn anything else and It still has hype from those early days (2005-2009).
It was also a nightmare upgrading the versions of it. It faded out of popularity with most people for a reason.
There are better options today and even 10 years ago and not just Wordpress.
Dries is the founder of Acquia, whose products are all based on or related to running Drupal websites.
Dries was the keynote speaker at DrupalCon Barcelona last month, where he discussed the new features currently under development in Drupal: https://www.youtube.com/watch?v=Wce6FkNN2Io
> It was also a nightmare upgrading the versions of it.
This was an issue prior to version 8. All major versions since then have been directly upgradable. It usually takes me 2-3 hours to do a major version upgrade. Maybe a few more if there's a lot of custom code.
The delta going from Wordpress to Drupal is quite big, it's been few years, but I remeber quotes for Drupal 8 projects being a few times larger than quotes for Wordpress based projects.
Most WordPress customers aren't so much locked into "WordPress", the application, but rather a provider of WordPress with a custom CMS. Unless their provider switches, they aren't really enabled to consciously protest WordPress.
This goes for both WP Engine and Automattic. Could be the reason why both are comfortable going nuclear on each other - they know their users don't have an easy alternative.
>> "Could be the reason why both are comfortable going nuclear on each other - they know their users don't have an easy alternative."
I've followed this from the start and as best as I can tell Automattic is the only side that went nuclear. WP Engine sent a C&D, then filed a lawsuit when the attacks persisted, and seems to have gone quiet since then aside from responding to the takeover of ACF.
WP Engine's response is how I expect a professionally-run organization to handle things: address technical issues as they pop up while continuing to provide the service people pay for, but otherwise quietly wait for the trial. Meanwhile there's a new bomb lobbed from Matt Mullenweg 1-2 times a day at WP Engine, the WordPress community, individual contributors, or some combination while Automattic employees are out doing the work of a PR department.
These things take time to sort out. Anyone moving platforms now, due to the drama, isn't going to show up in surveys/polls until after they've migrated. And depending on the size of their site, a migration could take the better part of a year. I expect we'll see how the sands are shifting by next July.
Drupal still has a very high learning curve. I'll use Drupal over WP any day, but I can acknowledge it has some rather rough edges.
I haven't dug into it yet, but I think that "starshot" initiative that's been Drupal.org's front page since the last DrupalCon might be aimed at giving people an option without the rough edges.
Personally, if Wordpress handled security alerts with plugins the way Drupal does, and if they did a better job of keeping bad code out of plugins (why can a theme implement a form?? At least that was the case years ago. Has it changed?) I'd give WP a serious look again.
Drupal peaked in like 2009. It’s mostly built by “click monkeys”, as you can do a lot by clicking around the UI to build stuff. But it’s old and even the founder abandoned it long ago around 2012.
people use it because they didn’t learn anything else and It still has hype from those early days (2005-2009).
It was also a nightmare upgrading the versions of it. It faded out of popularity with most people for a reason.
There are better options today and even 10 years ago and not just Wordpress.
> But it’s old and even the founder abandoned it long ago around 2012.
Dries is still using Drupal. Here is his personal blog, where he discusses updating to Drupal 11: https://dri.es/drupal-11-released
Dries is the founder of Acquia, whose products are all based on or related to running Drupal websites.
Dries was the keynote speaker at DrupalCon Barcelona last month, where he discussed the new features currently under development in Drupal: https://www.youtube.com/watch?v=Wce6FkNN2Io
> It was also a nightmare upgrading the versions of it.
This was an issue prior to version 8. All major versions since then have been directly upgradable. It usually takes me 2-3 hours to do a major version upgrade. Maybe a few more if there's a lot of custom code.
> It’s mostly built by “click monkeys”, as you can do a lot by clicking around the UI to build stuff.
Isn't this an almost perfect description of WordPress? It hasn't seemed to have done any harm if that's the case.
> But it’s old and even the founder abandoned it long ago around 2012.
Are you sure? On drupal.org right now one of the main links is one of the founders in a keynote video presenting the newest version.
The delta going from Wordpress to Drupal is quite big, it's been few years, but I remeber quotes for Drupal 8 projects being a few times larger than quotes for Wordpress based projects.
Most WordPress customers aren't so much locked into "WordPress", the application, but rather a provider of WordPress with a custom CMS. Unless their provider switches, they aren't really enabled to consciously protest WordPress.
This goes for both WP Engine and Automattic. Could be the reason why both are comfortable going nuclear on each other - they know their users don't have an easy alternative.
>> "Could be the reason why both are comfortable going nuclear on each other - they know their users don't have an easy alternative."
I've followed this from the start and as best as I can tell Automattic is the only side that went nuclear. WP Engine sent a C&D, then filed a lawsuit when the attacks persisted, and seems to have gone quiet since then aside from responding to the takeover of ACF.
WP Engine's response is how I expect a professionally-run organization to handle things: address technical issues as they pop up while continuing to provide the service people pay for, but otherwise quietly wait for the trial. Meanwhile there's a new bomb lobbed from Matt Mullenweg 1-2 times a day at WP Engine, the WordPress community, individual contributors, or some combination while Automattic employees are out doing the work of a PR department.