has an issue. No, not that downside. We dwell in a submit peak world. peaked a while throughout Drupal Developer 8 development cycle. I’ve had conversations with fairly a number of individuals who really feel that we’ve misplaced momentum. Con attendances peaked in 2014, Google search impressions haven’t returned to their 2009 degree, core downloads have trended down since 2015. We have to settle for this and speak about what it means for Drupal Developer way forward for . Technically 8 is spectacular. Sadly Drupal Developer uptake has been very gradual. An element on this gradual uptake is that from a developer’s perspective, 8 is a brand new utility. Drupal Developer improve path from 7 to eight is one other issue. In Drupal Developer 5 years 8 was being developed there was a basic shift in software program structure. Throughout this time we witnessed Drupal Developer rise of microservices. is a monolithic utility that tries to do all the pieces. Don’t fret this is not making an attempt to rekindle Drupal Developer smallcore debate from final decade. In the present day it’s extra frequent to see an utility that’s constructed utilizing a handful of Laravel micro providers, a few golang providers and one constructed with nodejs. These Drupal 10 functions usually have a number of frontends; internet (react, vuejs and so on), cell apps and an API. That is extra effort to construct out, nevertheless it more likely to be much less effort sustaining it long run. I’ve heard so many excuses for why 8 adoption is so gradual. After a yr I believe it’s secure to say Drupal Developer group is in denial. 8 will not be as widespread as D7. Why is not this being talked about publicly? Is it as a result of there’s a industrial curiosity in perpetuating Drupal Developer fantasy? Are Drupal Developer companies constructed on providing providers frightened about scaring away prospects? Adobe, Sitecore and others would level to such weblog posts to assault . Certain, admitting we have now an issue might trigger some brief time period ache. But when we do not have Drupal Developer dialog we are going to go Drupal Developer means of Joomla; an irrelevant product that continues its gradual decline. must resolve what’s its future. Drupal Developer group is stuffed with good individuals, we ought to be speaking about Drupal Developer future. This must be a public dialog, not one thing that’s mentioned in small teams in darkish corners. I do not suppose we are going to ever see turn out to be a group of microservices, however I do suppose we have to turn out to be extra modular. It’s time for to pivot. I believe we have to minimize options and decouple Drupal Developer parts. I believe it’s time for us to get again to our roots, however modernise at Drupal Developer identical time. has at all times been a content material administration system. It doesn’t should be a content material supply system. This goes past “Decoupled (Headless) “. ought to turn out to be a “content material hub” with pluggable workflows for creating and managing that content material. We must always undertake Drupal Developer unix method, do one factor and do it effectively. This method would permit to be “simply one other service” that compliments Drupal Developer utility. What do you suppose is required to arrest Drupal Developer decline of ? What ought to 9 seem like? Let’s have Drupal Developer dialog. Drupal 10 Improvement and Assist