Drupal 8.0.0 released
I have very mixed feelings about Drupal. On one hand, it does have a lot of functionality available in third party modules; but the quality and completeness of them varies <i>wildly</i>, and most require custom code in order to be useful.<p>Another issue is maintenance. I don&#x27;t think I&#x27;ve ever met a well-maintained contrib module; even ones that seem to be actively maintained aren&#x27;t what I would call &quot;well&quot; maintained...reported bugs don&#x27;t get fixed, patches don&#x27;t get accepted or commented on (I have a half dozen bugfix patches spread across three or four projects, including one for something in core, that have gotten no response, some for months). While Drupal doesn&#x27;t suffer from the crass commercialization that has befallen much of the WordPress ecosystem, it seems only companies paying for development get any sort of response. I don&#x27;t have a problem with developers prioritizing paying customers (I do it with my own Open Source software, as well); but, when someone sends a patch that fixes a bug, at <i>least</i> comment on why you don&#x27;t want to integrate it or give some guidance on what would make it acceptable for integration. I am beginning to feel like submitting a ticket to the Drupal issue tracker, even with a patch to fix the problem I&#x27;m reporting, is a waste of my time. If it were one project or module, this wouldn&#x27;t be such a big deal; individuals get busy. But, I can&#x27;t think of any Drupal module or project that I&#x27;ve ever had a good experience reporting issues on. And, if I didn&#x27;t know that development is still ongoing, and that many new sites are being developed with Drupal, I would assume this extraordinarily poor level of interaction in the tracker was indicative of the impending death of the project.<p>There is also an academic love of complexity and abstraction in Drupal, almost to the point of absurdity, at times. Every new release introduces vast swaths of new terminology (often used in ways slightly unlike the rest of the industry use the term). Entities, nodes, rules, entity bundles, content types, views, entity references, delta, features, fields, hook, machine name, taxonomy, etc. About half of these do not mean what I would have guessed or are used in subtly different ways from what I would have guessed. And, it&#x27;s impossible for a casual Drupal developer to stay on top of this stuff; it moves so rapidly, and is so poorly documented, one has to read code. And, there&#x27;s a <i>lot</i> of code. Somehow, despite all the abstraction, most modules include huge swaths of code, and aren&#x27;t particularly re-usable. Even very simple functionality seems to require pages of code. It&#x27;s often more of a pain in the ass to make the re-usable components work in some way that the developers didn&#x27;t think of than it is to implement from scratch. Partly this is my own shallow knowledge of Drupal, but I see experts building out entirely new modules to address very similar use cases to other modules they&#x27;ve made, so I&#x27;m not alone. Somehow, despite WordPress&#x27; much uglier code base, I&#x27;m generally able to implement stuff more rapidly than in Drupal; and many things that seem really locked down and hard to change in Drupal seem easy in WordPress.<p>The upgrade path is literally disastrous for non-core modules. One literally can&#x27;t get from point A (a Drupal 6 site) to point B (a Drupal 7 site) without writing a lot of migration code, unless you&#x27;re only using the most basic of core functionality. I&#x27;m months into a migration from D6 to D7. The new(-ish) Migrate module requires writing code, sometimes significant amounts of it, and is extremely poorly documented (and uses a bunch of its own jargon in confusing ways; the number of contexts in which the word &quot;migration&quot; is used for different purposes makes my head explode), and in-place upgrades don&#x27;t exist for a large number of modules, including pretty important ones (like Project Issue, the module used by Drupal.org for its own issue tracker...it has no working upgrade path, at all).<p>I see the benefits that Drupal 8 brings. And, having worked with Drupal 7 for a few months now during this migration, I see that the direction is a positive one. But, I find myself being angry a lot whenever I work with it, because there&#x27;s so much forward momentum (everything changes! all the time!) but nobody seems to give a shit about bugs, major usability problems, or providing a reasonable upgrade path. Really basic stuff that ought to go without saying, really doesn&#x27;t in Drupal.<p>So, it&#x27;s a real love&#x2F;hate relationship. Which is true of every CMS I&#x27;ve ever used (and I&#x27;ve used a lot). I have decided to stick with Drupal through at least one more iteration and will launch our Drupal 7 site in a few days (if I&#x27;m lucky), but I don&#x27;t know if I&#x27;ll ever migrate to Drupal 8.