I'm not sure words can describe how mission critical this is if the Drupal project wants to keep being a leader in its industry. What irritates me is how Drupal 7 essentially had this--at least in concept; it's one of the reasons Drupal 7 was one of the most popular CMSs that existed--but when everything headed into Drupal 8+, the clique responsible for mandating Composer (as if it was some sort of new Velcro) kept dismissing the concerns everyone had about its forced usage. That's when everyone should've realized that Drupal had become hijacked and how it was essentially being held hostage by a cute little group of gatekeepers who clearly cared little for everyone else who wasn't deep-throating whatever development nuance they believed everything revolved around. Thankfully, this demo makes it look like it's been wrestled back into the hands of those who have some common user sense when it comes to user experiences because nobody who uses Drupal--in any capacity--be they themers, module developers, core developers, or just people who want to try things out--should be forced into using anything that isn't a core capability OUTSIDE of core via third-party non-core apps like Composer. Whoever thought that'd go over without any fuss or believed that everyone involved in using Drupal would just dismiss it, forget about it and move on, or kowtow to whatever kind of conceptual Drupal panacea they believed was being manifested by forcing it, should never be allowed within 100 miles of using Drupal ever again. This demo gives me hope that there's still reasons to stick with Drupal. I hope it gets delivered into real, production-grade incorporation because if it does, it could single-handedly return Drupal to a popularity it's been missing ever since leaving version 7.
Thank you :)
I'm not sure words can describe how mission critical this is if the Drupal project wants to keep being a leader in its industry. What irritates me is how Drupal 7 essentially had this--at least in concept; it's one of the reasons Drupal 7 was one of the most popular CMSs that existed--but when everything headed into Drupal 8+, the clique responsible for mandating Composer (as if it was some sort of new Velcro) kept dismissing the concerns everyone had about its forced usage. That's when everyone should've realized that Drupal had become hijacked and how it was essentially being held hostage by a cute little group of gatekeepers who clearly cared little for everyone else who wasn't deep-throating whatever development nuance they believed everything revolved around.
Thankfully, this demo makes it look like it's been wrestled back into the hands of those who have some common user sense when it comes to user experiences because nobody who uses Drupal--in any capacity--be they themers, module developers, core developers, or just people who want to try things out--should be forced into using anything that isn't a core capability OUTSIDE of core via third-party non-core apps like Composer. Whoever thought that'd go over without any fuss or believed that everyone involved in using Drupal would just dismiss it, forget about it and move on, or kowtow to whatever kind of conceptual Drupal panacea they believed was being manifested by forcing it, should never be allowed within 100 miles of using Drupal ever again.
This demo gives me hope that there's still reasons to stick with Drupal. I hope it gets delivered into real, production-grade incorporation because if it does, it could single-handedly return Drupal to a popularity it's been missing ever since leaving version 7.
Automatic updates are a big risk of damaging your site at the most inconvenient time.