5 ms·
I think conversely that Drupal 8 is the swan song. Too late to the party. Everyone who was really unhappy with the spaghetti bowl of code in prior drupal versio
by ams6110 11y ago
I think conversely that Drupal 8 is the swan song. Too late to the party. Everyone who was really unhappy with the spaghetti bowl of code in prior drupal versions has already moved on. Those who have not, are not interested in rebuilding their sites on a new platform. They just want Drupal 6 to keep working.
Drupal 8 is not a gentrified neighborhood, it's more like the ghost cities in China: clean, modern, well-designed -- and empty.
- ogsharkman 11y agoDrupal 8 is not a gentrified neighborhood, it's more like the ghost cities in China: clean, modern, well-designed -- and empty. I'm digging this analogy.
- monk_e_boy 11y agoI don't find Drupal 8 that nice. It still uses crappy render arrays ('#var_name' => 'value') ... really? Ugh. It still has random errors, our module stopped working because of a cache corruption. How does that even make sense? Clear cache is now needed to get twig changes to propagate. Man. That is so slow and so pointless.
- ogsharkman 11y agoI'm not familiar with Drupal at all, so I believe you. I just liked the analogy. :)
- snowwrestler 11y agoIt's 1.0 software, essentially. I've got several D7 sites, and I'm not even planning to look at D8 until the fall. Thanks for finding all the early bugs for me, though. :-)
- thrillgore 11y agoI'm probably not going to move to D8 until there are concrete plans to retire D7. Which is still something being discussed in the community.
- lightlyused 11y agoTook me about 2 seconds to find this: Disable Drupal 8 caching during development https://www.drupal.org/node/2598914 https://www.drupal.org/node/2598914
- monk_e_boy 11y agoYes. It took all of us 2 seconds to find it when we realised it what was happening. You're not the first person to type stuff into google.
- lightlyused 11y agoExcept that analogy is wrong.
- daxfohl 11y agoWhat have they moved on to? I'm investigating CMS's for a client (an task I have entirely no experience with). Is Joomla any better? Or is the whole concept of CMS dying?
- monk_e_boy 11y agoCMS is dying. We find it's easier to have a separate blog, shop, photo site etc than try to stick it all in Drupal. After ditching our custom CMS software for Drupal, we find we spend more time making Drupal do what we need than just starting a site from scratch.
- busterarm 11y agoWordpress powers 1/4 of the internet... Any company with a decently sized content (producing) team is going to need to use a CMS. A lot of folks are also using Hubspot and Salesforce to create their sites...Gotta love vendor lock in.
- monk_e_boy 11y agoI wouldn't count wordpress as a CMS personally, more of a super blog. Drupal is much more powerful and flexible (out of the box -- you can modify both)
- jordanlev 11y agoMore people are on wordpress than any other CMS, which is one data point in the decision but certainly does not mean it's "the best". But based on the wording of your question ("which have they moved on to"), this is probably the closest correct-ish answer. Other than that, people have moved on to all sorts of CMS's: * If you're looking for something in the spirit of Drupal (most configuration done via dashboard interface, very flexible content modeling), try ProcessWire (http://processwire.com/ http://processwire.com/) (free/open-source) * If you're looking for something more designer-friendly and have a budget for the project, Craft CMS (https://craftcms.com/ https://craftcms.com/) is very popular these days. * Also designer-friendly and less complex than Craft (and less expensive), so it's better for simpler sites: Perch CMS (https://grabaperch.com/ https://grabaperch.com/). * For the most easy-to-use editing interface, I recommend Concrete5 (http://www.concrete5.org/ http://www.concrete5.org/) -- my personal favorite (free/open-source). * If this is a super basic site though and you just want to use an off-the-shelf theme and let the client manage it as much as possible, you're probably best off with a hosted solution such as Weebly (http://www.weebly.com/ http://www.weebly.com/) or Squarespace (http://squarespace.com/ http://squarespace.com/). These have monthly fees (but comparable to decent web hosting). There's also 18 bajillion other options out there... welcome to the world of CMS's, where we had decision fatigue long before javascript made it cool ;)
- thesnufkin 11y agoI wonder what you base this statement on. As someone who has worked almost exclusively with Drupal, I have been always been conscious about being on an island, concerned about my lack of understanding regarding other frameworks, languages etc. Because of this, I am constantly looking for the signs that would indicate that Drupal is falling, yet I still have to find these. Admittedly, since I work for a company which has Drupal as its core business, I am biased. To avoid this bias I was doing a little research for statistics. I checked the usage of Drupal core [1] and I found it somewhat misleading (e.g. there is a significant jump around the time of the release, so the statistics on such short term must be skewed due to test installs). Instead I looked at ctools, which is a dependency for several contributed modules and is the top used module [2]. This shows significant growth since the start of 2016. So it is growing, people are using it. But most importantly, the numbers for Drupal 6 stay the same. So it seems that people who have a stable website are happy with it, and new users are likely to jump on the Drupal 8 train. Also let us not forget the same voices were heard when Drupal 7 came out, coupled with the unexpected lag of contributed module availability. With a lot smaller API change, people found they have to wait 6-12 months after D7 was released to start building Drupal sites. Contribs, e.g. Views has released an RC for Drupal 7 on June 17th, 2011 [3], when D7 came out on the 5th of Jan, 2011 [4]. Views is just one of the important contrib modules (now in core), and people had to wait 6 months to use it! The contrib upgrade curve seems similar, if a little bit faster for Drupal 8. But having most of the important contrib modules in core, this impacts new builders less. About the state of the spaghetti: frankly I don't think that customers care too much about it (after all, Wordpress does own a significant share of the market ;)). Developers do. Customers care as well, but mainly to the extent of maintainability and cost implications. And I think with personal bias aside, Drupal 8 is much better on this front, than Drupal 7 (although there is still work to be done, procedural code to kill), it does deliver a framework, which allows a wider range of developers to start working with it, using familiar patterns and frameworks (PSR-4, Symfony). Long story short, I don't hear the swan song. But I'm happy to keep my ears open :) [1] https://www.drupal.org/project/usage/drupal https://www.drupal.org/project/usage/drupal [2] https://www.drupal.org/project/usage/ctools https://www.drupal.org/project/usage/ctools [3] https://www.drupal.org/node/1192186 https://www.drupal.org/node/1192186 [4] https://www.drupal.org/node/1015392 https://www.drupal.org/node/1015392