Drupal dating software
And debugging things on the frontend—well, I'll get to that soon.
The overarching issue is that the Drupal community was sold on the idea that moving Drupal to Symfony would pull in thousands of other PHP developers who would flock to Drupal once it started using a more modern code architecture.
We're the leading open-source CMS for ambitious digital experiences that reach your audience across multiple channels.
Because we all have different needs, Drupal allows you to create a unique space in a world of cookie-cutter solutions.
Things became a bit harder in Drupal 8, because of two things: And these two problems kind of fed into each other—not only did module authors had to often rewrite (or at least radically alter) large swaths of code to support the new Drupal 8 APIs, but they also had to scrap any hook_update() upgrade implementation they may have worked on once that change record was published.
I'm not speaking in the hypothetical here; this is what happened with the Honeypot module.
But Drupal 8 is actually a really good choice for those who build decoupled architectures using JSON: API, or Graph QL, or whatever other fancy decoupled framework and need a reliable content backend.
To be honest, though, it seems that those who do 'decoupled' with Drupal are often people who started with Drupal (or something like it, and then get the decoupled game. Drupal is a hard sell if you have a team of non-PHP developers (whether they do Node, Ruby, Python, Go, or whatever) and are looking into decoupled or otherwise buzzwordy architectures.
I'm one of the first to admit that this was probably one of the best and most necessary architecture changes in Drupal.
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.
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.
Along the same theme as the previous topic, Drupal rearchitected most of the foundational bits of code (the menu routing system, the HTTP request system, the Block system, the Entity system—pretty much everything except maybe Forms API) on top of Symfony, a very robust and widely-used PHP Framework.