Drupal dating software
This fact has been beaten to death, so you can read more about that elsewhere, or see the current usage graph here and yes, not every site reports back to Drupal.org, so those numbers are not perfect... So people are asking questions: post, in particular, was the following tweet by @webchick (Angie Byron), who coincidentally is probably the main reason I dove headfirst into the Drupal community many years ago after she mentored me through my first core patch (hi Angie!
): I won't answer all the questions above—there are a lot of nuances to each that I could not possibly answer in a blog post—but I do want to jot down a number of areas where I have seen pain (and usually experienced on my own) and which are still holding back widespread adoption of Drupal 8 by those who used to default to Drupal for 'all the things'.
That promise really never panned out, as if anything, it seems to find solid senior-level Drupal engineers nowadays (at least in my experience—am I wrong here? Some Drupal developers who are not classically-trained (like me!
I never took a comp sci class in my life) chose to expand their knowledge and grow with Drupal 8's new architecture.
Thoughts about Drupal 8, Drupal 7, Backdrop, the Drupal Community, Drupal Con's meteoric price increases, Drupal Camps, and the future of the framework/CMS/enterprise experience engine that is Drupal have been bubbling up in the back of my mind for, well, years now.
I am almost always an optimist about the future, and Drupal 8 promised (and usually But one thing that has always been annoying, and now is probably to the state of alarming, for some, is the fact that Drupal 8 adoption has still not hit a level of growth which will put it ahead of Drupal 7 adoption any time soon.
There's a massive initiative to make things better: [META] Improve Drupal's use of Composer.
Caveat to those who read on—you may think I'm trying to disparage Drupal through the rest of this post. I'm exposing the dark side of a major open source project's decision to radically re-architect it's core software on an entirely new foundation. a lot of people mention that because more people build custom Node.js-based single page apps using the MEAN stack, or now do hip and trendy 'full stack development', and Drupal is some old monolith, Drupal has been left in the dust.
It's helpful to know these things so we can figure out ways to avoid hitting all the pain points in the future, and also as a sort of 'call to action' in case anyone reading this thinks they can push some initiative forward in one area or another (it's no coincidence I'm finishing this post on the flight to Drupal Con Seattle! I don't buy that argument, because otherwise we'd see similar attrition in pretty much all the other PHP CMS communities... Sure, there are use cases where someone would consider a hip trendy decoupled web framework backend.
Others chose more familiar pastures and either moved on to some other PHP-based CMS or switched to some other ecosystem.
I don't blame them, not at all; it's a tough decision you have to make to balance your career desires and opportunities, and everyone has to make their own decision.