Encourage module developers to provide instructions for manually obtaining libraries. This boiled down to a cost benefit / cost of ownership issue. Time is money and if I have to spend less time on D7, then that's where I'll stay. In recent years, with the help of Digital experience platforms (DXP), global companies are focusing on creating a better digital experience that effectively … You can find plenty of arguments out there about how terrible Drupal is — that’s easy — but it’s not true. Just make Drupal work and with the fewest number of moronic inconveniences possible. (And it doesn't help for anything but a static site, like a brochure site.). Composer is again not made up thing from Drupal but widely adopted tool in PHP community. We’re talking in the range of hundreds compared to thousands for WordPress. They're not going there. In any case, the new architecture has more complexity than the old; and because of this, it's almost a necessity to adopt the following: Along with all the other changes, Drupal's theme system was completely swapped out—it went from using the unholy monster that was PHPTemplate to a clean, new, standard system from Symfony, Twig. Reinstate drush dl [project] and drush pm-update. To be honest, Drupal 7 needed the overhaul that became Drupal 8. It's a great tool, no doubt about that. https://www.drupal.org/project/libraries. If so, get ready for one team member to be the designated DevOps person because now complexity goes up a fair amount. Make it easy and pleasurable to develop websites and content-focused back-ends for web services in Drupal. We won’t deny that Drupal is complex, especially compared to WordPress, but it’s because of that complexity that it has a lot of advanced functionality as well. I was amazed at simple things how based on different context different blocks were being served and nobody was setting up blocks directly. Reported in August 2012, first patch was submitted in November 2012, still not fixed, #1329742 Autocomplete with tagging silently discards invalid input I rebuild websites faster with Laravel than D8. Well I do feel sorry for people trying to use Drupal together with PostgreSQL. Case-in-point is Drupal Commerce. He works in our Falls Church, VA, HQ. There’s just way fewer of them vs WordPress. So... 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 not easy to say what all the reasons are, but Composer is finicky..security updates are more hassle because of more changes..’ But sadly the instability of the core isn't ready for those projects either. It would be a fun and devastating exercise to count the amount of time that has been wasted because of the patch based workflow. It's just more complexity that I really would rather not have to deal with and that wastes my time with no benefit that I can see. It is not intuitive and there has been a lack of focus on the user experience. I worked for a renowned company for years. And I don't blame them. Companies that provide commercial (micro)services do not bother to write integrations/tutorials/SDK's to Drupal themselves, but offer them for other languages/frameworks. Hosted Apache Solr and Server Check.in are both currently running on Drupal 7 (well, the frontend parts at least), and I have tens of thousands of lines of custom code which integrates with backend APIs (using things like Drupal's Entity API, Form API, Block API, Queue API, etc.). Here's a memo to anyone in favor of those things: the whole point of a system like Drupal is to make doing things, easier. Many of these were caused because modules were put into Core (like Views), and when they had a security issue, Core had to be updated. The simplest clean up tasks like removing a problem module from the system is now a complex task of removing various pieces from the db. Drupal needs to either bake composer into core, or fork it to specifically work with core. Features and context gone, symphony is in and You cant upgrade drupal6 or 7 easily to drupal8. That is, you have one codebase, maybe even on one server, and you can run many Drupal websites (each with its own database, set of modules, unique files directory, theme, etc.). Others chose more familiar pastures and either moved on to some other PHP-based CMS or switched to some other ecosystem. In reply to So far, everyone has by bluepresley@ga…. But building a site with a huge part of custom code? But this is in many cases the straw that breaks the camel's back. 5. You can't resolve two decades worth of architectural assumptions and dependency cruft in one major release. And yes, the legacy ,knowledge and community should be considered. The good thing about WordPress is that you can handle most tasks by yourself, provided you know where to look. Drupal should work without all of them, right out of the box, no fuss, no muss. Drupal has a reputation for being strong in functionality and having a strong community, but weak when it comes to design. Sure, there are use cases where someone would consider either Drupal or a hip trendy decoupled web framework backend. The weirdest thing for me is that Drupal is still based on patches instead of pull requests. The admin interface can be customized, but that carries additional cost, and plenty of work. #1064882 Remove syscalls from calling date_default_timezone_set(), date_default_timezone_get() Nate Haug is another who understands both sides but the community lost him too. I'm with you on all points. I've tried porting existing sites, and creating new sites in Drupal 8. Honestly, we could have already spent half that, and I move them to Wordpress. There is an open issue in the Drupal project issue queue to help improve this situation, but we're far from the end game here: [Meta] Better support for D7 -> D8 contrib migrate. It is free to be used by any blogger or developer. If you start new, start with 8. 4) Change their philosophy on goals. It is not possible to keep all happy, small, medium and big consumers of Drupal. They tried some with the release of Drupal 7, but need to do the process over again because it's still mainly rather poor. Dries is awesome, but he's entirely too cautious as a leader. For what it's worth, my biggest hindrance to Drupal 8 adoption has been the "C" word (composer). Who do you think wins? If 7 is stable, what is the issue? Now it's a niche platform, overly complex and is dying rapidly. If that's how I wanted to develop, I'd have selected a framework like Laravel, NOT a bloated, cumbersome, archaic CMS like Drupal. There are other practical applications; ‍♂️. You can only make things right by ackowledging what needs to be made right. I believe we could hide some of the complexity and have a Drupal 8 that still works for the likes of me. It's baffling that something like this keeps being ignored but says everything about why Drupal is in the dire straights it's in. In reply to I could have predicted these by Mike Schinkel. Drupal may be good, but it isn’t easy to use, manage, or maintain. #2564307 [meta] Remaining Drupal 8 PostgreSQL issues ), Part of this is identifying what makes Drupal uniquely better than other systems and what its audience is, and that is the content development and site-building experience, the content modeling and views, the module ecosystem and flexible, combinatorial way in which modules work together as a set of flexible building blocks. We are pretty late here btw. For example, Drupal is free to download and anyone can modify and extend the platform. Drupal has pretty good caching (though obviously it's not making things easy for Bradley!) Warning messages from php is just an everyday part of life and you have to simply hide them and they keep filling up your logs. Thanks to composer, OOP, slow performance and many other stupidities. (Please RT.). Sure, you get a 1964 big block Chevy motor with a chassis that's easy to work on, but if you want the new LT2 engine and electronics package to boot, you'll have to find another platform. Drupal 8 has all of this, and could with some imagination be packaged in a way that would let me continue using it for the kind of sites I regularly build. Long gone are the days of downloading a module and FTPing it to the site. Composer, like Drupal 8, just works. If, however, video is not your favourite medium, there are also many written tutorials and guides available to get you started. I never took a comp sci class in my life) chose to expand their knowledge and grow with Drupal 8's new architecture. - Understand a whole lot of concepts with very unintuitive vocabulary if you want it to be any useful The number of site builders Drupal is going to lose far, far outweighs the number of Symfony developers they might gain (especially as the latter number is likely to be zero. All content copyright Jeff Geerling. I develop at least 10+ Drupal sites a year with complex data processing that involves heavy use of modules like Rules. There's a massive initiative to make things better: [META] Improve Drupal's use of Composer. I had to dig through custom module code. For example, if you need to display and organize tens or hundreds of thousands of disparate content items, that could be a situation where Drupal … Drupal 8 is a very different framework and platform than Drupal 6 or 7 was. Greatest problems? Drupal isn’t bad, Drupal is good. Drupal hosting companies will make it easy to get set up, and help you run updates. When I was following Drupal during the times of developmentseed. It's 2019 as I write this...I don't see the deployment complexity being significantly resolved for at least another three years. If you remove Git, Composer, Drupal console, Drush, what you get then? A large community, even a nice one, doesn’t equate a highly-skilled one. I started out as a complete newbie on Drupal. And composer nightmare.. hours spent every month trying to clean up composer messes. We're now started working with various players in the ecosystem to launch a solution - A collaboration of various agencies, hosting companies and our site builder (www.cohesiondx.com which cuts the effort in theming Drupal sites by 80%). It powers several thousand applications and websites. 2) Composer. But this meant that large swaths of Drupal experience were thrown out the window. While Drupal themes do exist, most Drupal websites sport a custom-coded theme, or at least a highly customized theme. I'm almost $200 bucks an hour, and I'm no closer helping them achieve their goals to move to D8 than when I started.. (And, I've been developing Drupal solutions since early D5). But having one standard way to build and maintain Drupal codebases will be better in the end, because right now it can be quite messy, especially for those who downloaded Drupal as a tarball and use no CI system. 5. The rest of us don't think it's fun. 3) Agile development. A kind, funny, inclusive, and determined community will attract tons of people of all skill levels. This isn’t exclusive to the Drupal community though, and we should see “the community” for what it is: marketing. I agree with 99% of this article. I haven’t found a reason to use Drupal since. For example many payment gateways in Drupal Commerce are outdated. Things like that seem to be much more focused on programmers self-pleasuring by automating all teh things because they can and because they think it's fun to do than actually solving any real problems of building a website. Now that may sound like a bad thing but I think it's the right direction for Drupal to go in. 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... but it's the best data we have to work with. Views, Media and Page Builder could have been added to D7 core. Nobody likes popups, so we waited until now to recommend our newsletter, a curated periodical featuring thoughts, opinions, and tools for building a better digital world. Anyone who says they know the solution before they know the problem is lying, wrong, or guessing. Caveat to those who read on—you may think I'm trying to disparage Drupal through the rest of this post. On the current project, we are doing that. Drupal sites vulnerable to double-extension attacks. recently a friend of mine ask me to create a website and I re-take Drupal 8. Drupal (as an organization) never respected the fact how their decisions would affect the budgets of those who had heavily adopted in them before.. ... for a while, my organization tried HARD to stay with Drupal.. According to w3techs, Drupal powers about 1.7 percent of all websites, which is good enough for second in the list of content management systems. Jeff, Flexible and highly scalable, Drupal publishes a single web site or shares content in multiple languages across many devices. Drupal 8 fosters this mentality towards contribs so the contribs end up being these lackluster gui hacks for the non-devs because "there has to be a gui but the real power is in the code". In reply to Sadly I am coming to a by DeveloperChris. But that still leaves us with needing senior devs, as you say, to accomplish much of anything in the theming layer. Drupal 7 suited my needs for ambitious but smallish community and business websites, primarily because of a large stable of mature modules, an awesome way to model content and create custom content types, and of course Views. I am almost always an optimist about the future, and Drupal 8 promised (and usually delivered) on many things: 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. I'm a little late to the party, but here are my thoughts on D8: 1) 4 yrs later, it's still very buggy. There's no doubt Drupal 8 has a great feature set, a thoroughly-tested core codebase, is excellent as a general site-building tool, and is primed for the building great (and 'ambitious') digital experiences. That promise really never panned out, as if anything, it seems harder to find solid senior-level Drupal engineers nowadays (at least in my experience—am I wrong here?). First you lost people who liked Drupal because it was simple and did not want to have to learn how to become more advanced programmers, and secondly you'll never gain the people who are advanced because they already have better options in the advanced arena that have none of the baggage of negative opinion about prior versions of the platform. Drupal is really great. And... cater to your audience! Fixing the theming so that it's easy to control all the html output, mostly from within the admin interface (which is fine now that we can easily export and backup the config), would be a HUGE change for Drupal. Wordpress has won. In other words, the defacto ecommerce platform is only easily usable for programmers. The architecture of D8 is not in question, at least not for me. I've been having a rough time getting used to debugging Drupal 8. Between GIT, Composer, Drupal Console, and Drush; all these things should be optional. Drupal 8 upgrade evaluation is a good place to start. It never crossed my mind to put up a page with my CV or family pics. Should I stick with D7 LTS support for years and years, and re-platform on something else if I ever get the budget? We should have much earlier start with the adoption of new things. Drupal is a good choice for large, complex websites. I didn’t need to be part of a Craft community to become productive in a Craft project, I just had to read their documentation, and since the system is more intuitive everything was easier. D8 and D9 may be a superior technological solution (compared to D7 and before).. but Drupal, any version, will now die, because it failed to take into consideration how it affects business decisions.. Riddle me this: If it takes $200,000 to upgrade a D7 version to a D8 version when I can just recreate the application from the ground up in Wordpress for $50,000? In fact, I would argue that the use of Composer made that even better. It’s worth noting that Drupal didn’t invent modules, nor is it the only platform that has a concept like modules. It depends on the project. Drupal development is abysmally slow. To mitigate this, it will be a combination of the initiative that is teaching composer to update Drupal more easily plus hosting companies continuing to offer "out-of-the-box" configurations that help developers with the above. #Content Management. Sayviget, When and How to Use Vue 3.0 with Craft CMS, Monitor Site Speed With Chrome UX Report and Google Apps Script. Open-source; Anyone can install and use Drupal without any costs. There are some massive benefits, like the fact that it is easier to use modern programming paradigms, dependency management tools, and site architecture. A 'Block' was still a 'Block'... but the way they are built changed from weird-but-conventional Drupal hooks to using 'Plugins'. Here's the rub: Multisite architecture is kind of in conflict with some of the core ways Composer works. I am still optimistic about Drupal's future, especially as the plan seems to be to not make such a massive set of architecture changes in a major version again, but instead to upgrade subsystems here and there through point releases. Test coverage is a theological doctrine imbibed by people who learned C++ or Java at university. Drupal has great standard features, like easy content authoring, reliable performance, and excellent security. But I think the moral of Drupal's saga is if you revamp many major portions of an ecosystem's architecture in one release, you have to accept the attrition that comes with such a refactoring. It is enterprise-class software: In terms of scalability, flexibility, reliability, manageability, security, … Take a look at the Stack Overflow Developer Survey Results 2019, more specifically "Most Loved, Dreaded, and Wanted Web Frameworks", you'll see that Drupal tops the most dreaded category. There are great developers who contribute to Drupal, but there are many more site builders who do not contribute any code. Projects can then be hosted on the same server (etc. Amazing stuff can be built today using API back-ends and superior JS frameworks on client side (or some static site generators). Yeah, it's a very nice tool to manage dependencies. If you just want to let us know what you think, find us on twitter @viget, leave us a comment, or tweet at me directly @poettersbetter. I view every significant architectural change in D8 as necessary, and in the long run, advantageous.