59
u/nixle Jan 05 '11
The thing I love most about Drupal is that it isn't Joomla.
19
u/d0odx Jan 05 '11
both are pretty horrible.
8
u/ShrimpCrackers Jan 05 '11 edited Jan 05 '11
I think Joomla and Drupal are too bloated and when you're on a shared host and both often break.
Most sites in my experience do well with Wordpress. I know I know, it's "just a blog platform" but seriously... most sites don't need that much complexity for the user. Besides, Wordpress has stable plugins that can handle many authors with multiple permissions. As for hits, wp-cache and others do a wonderful job. Wordpress has a lot of great qualities while Joomla and Drupal just brings optional quantity.
21
u/skeww Jan 05 '11 edited Jan 05 '11
Wordpress isn't a lightweight compared to Drupal.
X:\wordpress-3.0.4>cloc * 565 text files. 563 unique files. 7 files ignored. http://cloc.sourceforge.net v 1.53 T=9.0 s (61.8 files/s, 23006.2 lines/s) ------------------------------------------------------------------------------- Language files blank comment code ------------------------------------------------------------------------------- PHP 291 20399 41225 97013 Javascript 159 4159 2619 22097 CSS 88 2381 479 14448 HTML 17 258 7 1927 XML 1 7 0 37 ------------------------------------------------------------------------------- SUM: 556 27204 44330 135522 ------------------------------------------------------------------------------- X:\drupal-7.0>cloc --force-lang="PHP",module --force-lang="PHP",install --force-lang="PHP",inc --force-lang="PHP",engine * 852 text files. 847 unique files. 221 files ignored. http://cloc.sourceforge.net v 1.53 T=10.0 s (62.9 files/s, 22984.2 lines/s) ------------------------------------------------------------------------------- Language files blank comment code ------------------------------------------------------------------------------- PHP 404 14828 66433 127260 CSS 116 810 1098 8909 Javascript 84 815 2808 5085 Bourne Shell 8 172 3 1060 XML 12 3 0 441 HTML 3 4 0 69 ASP.Net 1 3 0 40 SQL 1 0 0 1 ------------------------------------------------------------------------------- SUM: 629 16635 70342 142865 -------------------------------------------------------------------------------As you can see, Wordpress isn't significantly smaller. Wordpress is merely ~24% less code (with ~38% less comments).
Edit: I didn't include the "test" files, since these are unit tests and the code is never executed on a regular website.
10
u/bananahead Jan 05 '11
I agree with you that wordpress isn't as lightweight as it seems, but SLOC is not a real great metric of anything.
4
u/skeww Jan 05 '11
Feel free to provide a better metric.
It was meant as a ballpark figure. Many people seem to assume that Wordpress is something very light and compact, which it certainly isn't.
There are almost 100 files with almost 100k lines of code. It's quite a bit of stuff.
1
Jan 06 '11
better metric? How about the fact that all drupal and joomla sites on shared hosting running slow as fuck, even if they are optimized to hell and back. Wordpress has no such issue whatsoever.
I dumped all joomla shit I had long ago. Not only is it bloated and slow as fuck, it is impossible to plug every god damn security hole in it, and it's only a matter of time before your site is hacked.
→ More replies (3)6
u/TylerEaves Jan 06 '11
Guess what...how useable it is on your shitty ass $5/month shared hosting is pretty much irrelevant to people doing real sites.
→ More replies (2)→ More replies (6)-1
u/ShrimpCrackers Jan 05 '11 edited Jan 05 '11
As you wrote; 24% less code is actually very significant considering Wordpress does pretty well with very few plugins (since a big chunk of that extra code is to make things incredibly easy for the user to configure and edit while Drupal requires a lot more work to streamline since the framework itself isn't enough and is much easier to break.
As for the comments, it's dubious to compare them directly without ratio. By ratio of comments to code, Wordpress scores about 4/10 while Drupal is 5/10. That said, I think Wordpress documentation and support is leagues better than Drupal regardless of numerics.
At the end of the day, it's a lot easier to train users to use Wordpress over Drupal, Drupal breaks more easily, Wordpress is a lot faster to deploy. So Wordpress wins for many smaller sites and can be used even for large scale websites depending on what you want to do.
4
u/Shocker88 Jan 05 '11
Documentation in Drupal has improved a lot of late and thus is likely on par - the shear scale of the framework within drupal makes it hard to directly compare. For basic content management I'd say Wordpress wins out in that it's a little nicer to install plugins for an admin and content changes/additions is nice and easy. Drupal module installs is a little confusing but the content changes/additions is likely on par with Wordpress with 7.0 due to many UX changes.
Whilst I'd say Wordpress may be a better system for smaller sites, or where admin might want to add some basic plugins, Drupal definately wins out for larger development based sites. Once Drupals framework kicks in and you learn to use the contributed modules correctly Wordpress really falls behind.
5
u/CritterM72800 Jan 05 '11
is much easier to break
I disagree with pretty much your whole comment but that part in particular is incredibly subjective and shouldn't be passed off as fact. I've broken WP far more often than Drupal.
9
Jan 05 '11
This. I think Drupal is kind of a terrible compromise.
On the one hand, if you want to use it to develop a rather simple content-driven site, you are better off using Wordpress.
On the other hand, if you are developing an advanced site which requires complex interactions with the user and non-standard features, then you'll need to write a lot of code to get everything to work properly... in which case I'd recommend using a proper framework like Ruby on Rails, Django or Cake and just build the whole thing from scratch.
20
u/Shocker88 Jan 05 '11 edited Jan 05 '11
Whilst most of the frameworks you provided help speed up the process, starting from scratch is rarely the fastest way to do it. It's also more prone to bugs and project scope blow-outs due to the whole project having to be scoped rather than a few key development/integration items key to that specific site.
Drupal and its contributed modules provide a relatively stable environment and rapid environment to base sites off to avoid 50-95% of the code overhead you'd otherwise require going with a framework. It does take quite a lot of time and experience to "learn" drupal and know how best to handle things. The one key issue with Drupal is things are done the "Drupal" way which is confusing as hell for people who haven't been working with it for months. The fact that being able to utilise the benefits of Drupal requires significant time learning the system is a critical issue with it as a whole.
I will agree with you that wordpress is a brilliant and easy to use platform for basic sites, and there definately is a time and a place for framework use, but Drupal can make the whole process a lot better for the majority of web projects you'll run into - just takes time to see it :(.
5
u/ShrimpCrackers Jan 05 '11
100% agree. The problem with Drupal though is that you need to afford a person or team to deal with it. Otherwise end-users even in large corporations will be stuck with a powerful tool with too many features to handle.
Meanwhile with Wordpress, the training is minimal and one can make a colorful post with just an email client. Perhaps that is an issue, make it too easy and you won't be needed? I personally think Drupal is a veritable cash cow for webdevs as a result.
So yes for basic sites, Wordpress all the way. Even for slightly more complicated sites, there probably is a Wordpress plugin for it. However for extremely special projects or services, Drupal is a decent development platform if too complicated to really spread outside of the web development team and sometimes taken for granted. For instance, there is nothing on the WhiteHouse.gov site that can't be done in Wordpress 3.
2
Jan 06 '11
Yep. The only other big grudge I had with Drupal, at least in development, is that I kept running out of memory every time I opened the admin interface, even after I had set my PHP limit to 64mb and it felt sluggish. Even my most complex Django code won't take 10% of the time the simplest Drupal based page took to load.
11
u/kitsune Jan 05 '11
I personally think this is a horrible idea if the major part of a site's administrative functionality is pure content management.
You do not want to write your own CMS.
Your CMS of choice + custom modules / plugins + integration paths to your specialiced apps built on your web framework of choice is a more sane way to live imo.
12
u/AlejandroTheGreat Jan 05 '11
You do not want to write your own CMS.
Every young gun developer who thinks they know better than the people who came before them should probably go through the motions of doing it all their way once, just to see what issues come up and why all these problems are hard and benefit from years of experience and a large userbase of testers. It's humbling and separates future good professional programmers from arrogant blowhards.
1
u/xaengo Jan 06 '11
This brings back old memories years ago when I had a terrific that I'd write my own CMS! We'll I never quite finished it, there was just too much. But like you said, a young developer learns much from trying to tackle something on such a grand scale.
4
u/boombatta Jan 05 '11
I think you're right about the advanced site in many ways, and I do like Django a lot. However, one great thing about Drupal is that you can build a complex site, and have an easier time finding people to maintain/change it. For a developer, it can be a pain, but for end-user/upkeep aspect, I think it's better than most. At least that's my experience, which I'll concede may be limited.
1
u/wshatch Jan 05 '11
You mean if I go with Drupal, I lose job security as well? :-P
3
u/ShrimpCrackers Jan 05 '11
Nonsense. Drupal is complicated enough that they'll need you anyway. Wordpress is too streamlined to demand a specialist or team in many mid-small companies.
1
Jan 06 '11
Actually, this is a fair point. It's easier to find cheap (don't know about good, haven't tried myself) PHP/Drupal devs, whereas Django freelancers come at a high cost. I sure know being one myself.
4
u/mirzu Jan 05 '11
I think Drupal is a great compromise.
TRUE: Wordpress or some of the other light weight cms solutions are better for simple sites. TRUE: Developing a very novel or complicated site is easier with Rails or Rails clone (*Rails).
However there are a large number of sites that are neither, and for a very large number of those sites Drupal is a far better solution than either Wordpress or *Rails. Sites with a modest amount of custom work, or that can leverage contrib modules heavily can be developed really quickly.
1
Jan 06 '11
Absolutely. I guess the sweetspot is "more than a blog, but still heavily CMSy". As soon as you start talking functionality outside of the (quite horrible IMHO) document model, things start falling apart. And don't get me started on theming... shudders.
2
Jan 06 '11
Building a whole system for managing content (no matter how complex) from scratch is rarely the best option, especially if you work on a team of people that need a common understanding of the systems inner workings. Drupal isn't perfect, it is bloated and it has a steep learning curve but once you get used to it you realize how powerful and generally well thought out it is.
2
Jan 06 '11
Well, what I'm thinking about is something more akin to a full website that does have some CMS aspects, and not a full CMS-like project. Throwing together the CMS part with Django/RoR would amount to less work than building the advanced stuff over the mess that is Drupal, at least in my experience. Drupal lends itself very well for building on top of the system, but try building sideways (unrelated features like, say, advanced user relationships) and you are stuffed.
2
Jan 06 '11
Yeah I agree. I think you hit the nail not he head with the "building on top vs. sideways" thing. That is a good thing to consider when trying to decide what platform to go with for your next project.
1
u/midri Jan 05 '11
100% agree for anything more complicated then a wordpress blog you need to be using MVC (just to keep shit sane!) Drupal's system is horrible! But it really is built for people that want a wordpress type site with more bells and wistles and damn be the consequences!
36
12
u/earwax2 Jan 05 '11
Would love to hear of any success or failure experiences from people who have upgraded from Drupal 6 to Drupal 7.
10
Jan 05 '11
This is dependent on several factors, such as quality of initial build, modules chosen, and amount of custom code. For a simple blog site without a custom theme, the upgrade should take about half an hour to an hour, but for a $500,000 website, obviously it's going to be a significant undertaking.
My general rule of thumb for Drupal upgrades is they will typically cost (either hours of $) about 35-40% of what they took to initially develop. It's definitely a significant undertaking for large sites.
10
Jan 05 '11 edited Jan 05 '11
Who uses Drupal for a $500,000 website?
edit: sorry to everyone I offended with this question? I have used Joomla! and Drupal for small projects and found both to be extremely limiting; I have always assumed that people with Real Budgets would choose to custom-build something whenever they could. Maybe I am really the one with the limitations!
19
Jan 05 '11 edited Jan 05 '11
Let's see.... examiner.com, the white house, fast company, loads of large government sites, the new york observer, the economist.
I'd be willing to bet every single one of those cost the organization more than $500,000 to implement, and in some cases it's easily a several million dollar project.
→ More replies (1)19
u/jc4p Jan 05 '11
Did you not watch the video on the site? A lot of big sites use Drupal as their base.
12
u/DrupalDev Jan 05 '11
Easy with the downvotes, this seems like a legit question.
Legit answer is: Even people with a lot of money don't like to waste it. Drupal allows to do a lot of things very fast (thus cheap) compared to other CMS or (god forbid) custom CMS.
4
Jan 05 '11
Sure, but I would assume that a $500,000 project would bring with it $500,000 worth of complexity. I also assume that too much complexity means that it becomes easier at some point to custom-build a solution than to customize a packaged (open source or off-the-shelf) solution.
I suppose that wouldn't be the case if you've got some awesome Drupal consultants to take on the project though...
2
u/DrupalDev Jan 05 '11
Fair points, but in the long run it's always easier to find Drupal consultants than people who have experience with your own custom CMS.
Getting used to the working environment is another place where you can greatly cut costs with Drupal (or other CMS). While all your new dev team members will have to learn how your CMS works, if you're using a common solution you can get people who already know how it works.
Combine this with the usually upheld standards of Drupal and you get a very efficient means of creating and maintaining even a complex website.
(Note that the same logic applies to Django and Joomla!, I just happen to prefer Drupal.)
3
u/jutct Jan 05 '11
Starting with a team that is strong in Drupal, $500k can go a lot farther than starting from scratch. Have you looked at the core API? That's a lot of code I wouldn't want to write from scratch.
→ More replies (35)2
Jan 05 '11
I create custom drupal sites for small business for under 10k, they can handle about 4 user at once nice and speedy. IF my server and drupal had to cater to 100,000 people a day, you better believe it would be a wisely invested half million. Long story short, if you have a highly customized drupal site, and it works, it's a totally different story when your custom code is put in the ringer of say, reddit.com traffic.
1
u/justaschmoe Jan 05 '11
We've been doing this on a small scale and it is annoying.... but this largely has nothing to do with core but (of course) the host of contrib modules.
Wysiwyg issues posed the biggest hang-up in my experience... but of course this was done with d7 release candidates and development versions of both core and modules. I'm excited to see how it pans out now everything is flush.
Even with these hiccups I already can't imagine returning to 6... media module is amazing, and while confusing at first the API upgrades (especially those dealing with Javascript) have been quite the boon to me already.
1
u/jutct Jan 05 '11
I had tons of trouble with some of the contrib modules and getting the output to look correct. It's very easy for a sloppy module developer to insert tags that override the WYSIWYG benefits. Once I had to start editing .php files to change CSS styles, I got very frustrated with it. Hopefully D7 fixes this, I'll have to check it out.
6
u/bitchkat Jan 05 '11
Only 32 modules I use don't have D7 ports yet.
3
u/bananahead Jan 05 '11
Out of how many?
They did a much better job than with D6. If I recall, that release dropped without a stable version of Views or CCK, which made it useless for 90% of people.
2
14
Jan 05 '11
The wise path is probably to hold off on upgrading until the flurry of early bug fixes is over.
5
u/Shocker88 Jan 05 '11
Kind of. The bug testing was pretty intense compared to most open source projects especially in the last few months (it was originally touted to come out over a year ago) bug fixing was thorough to ensure it functions. There's some known issues with small things using Postgres, however heavy testing has been done on the standard mysql stack.
I'd say the platform itself is stable enough for basic sites. I'd hold off on heavier development based sites to avoid the potential bug here and there and simply because the contributed modules that have flourished over the last 3 years for drupal 6 won't all have stable drupal 7 releases on day 1.
1
Jan 05 '11
No matter how thorough the testing, there's always going to be bugs that are revealed in the first few weeks of going public with any sizable software project.
1
u/Shocker88 Jan 05 '11
Definately, there'll be thousands of random use-cases that are unimaginable until someone decides to mix this with that. Fortunately with the testing however it's likely that an upgrade now won't be too big of an issue for a standard site (talking stock standard modules if any and a few pages of basically static content).
I'm obviously not advocating bringing across the monolith site that took months to build quite yet :P
Afterall there's no such thing as a "bug-free" system.
1
Jan 05 '11
It's true, we will see an influx of bugs now that it's 'in the wild'. However, there are several very large websites already running Drupal 7, including examiner.com which is currently hovering around ~40th in the world for traffic.I think it's safe to say that Drupal core is pretty damn stable at this point.
Where you are more likely to run into problems is less used contributed modules which have not had nearly as many eyeballs on them.
4
3
0
Jan 05 '11
[deleted]
5
u/ggggbabybabybaby Jan 06 '11
Play video games instead of upgrading.
3
u/redditor3923 Jan 06 '11
Check. Procrastinating work under the guise of "doing research" while still taking the "wise path". Being a developer does have its perks.
1
5
u/mikepixie Jan 05 '11
Time to upgrade my old Drupal 5 sites then...
3
2
u/bananahead Jan 05 '11
Yeah, I'm in the same boat. But honestly, you don't need to upgrade just because 5 is no longer officially supported. I'd weigh what new things 7 gives you versus the estimated pain of upgrading.
9
Jan 05 '11 edited Jan 05 '11
Wow. It looks like this is the dissenting opinion, but I've had a lot of bad experiences with Drupal and seriously bloated markup. Guess I'm the only one though.
2
Jan 06 '11 edited Jan 31 '16
zapzap
1
Jan 06 '11
Wait you want a Drupal site that's lean and scalable? No, you have to pay an expert for that...
4
u/midri Jan 05 '11
Every experience I've had with Drupal has been negative and I've worked on 30+ sites built on it. The "framework" it self is to blame IMO, it just does not require you do to things a specific way or the right way. Unlike frameworks like cake that try to get you to do things correctly (which is a hard thing to do to begin with because PHP lets you butcher anything you watch)
1
Jan 06 '11
It is easy to come out with bloated markup unless you are a fairly advanced Drupal dev. And it takes months to get to that level. I've been using Drupal for almost a year and every time I think I've mastered it something will throw me for a loop.
-4
Jan 06 '11
Drupal is bad because it's built using a bad foundation, PHP.
See this enlightening talk for more information about Drupal and PHPs Cobol-esque nature.
6
u/DrupalDev Jan 06 '11 edited Jan 06 '11
Wow you're on some kind of crusade, aren't you?
So, what should we use if not Drupal? Django? Some custom CMS?
Edit: Just finished watching the video. Most points have been addressed in questions, but I guess I can answer.
First part: Basically calls PHP hatred snobbery. That's you.
Second part: Most of this stuff is Not My Problem. These problems have been solved and addressed with various things, including Drupal as mentioned.
Almost all the things mentioned are resolved by Drupal.
-Internationalization : Yes
-Human URLs: Yes
-DB Queries: Yes
-Security: Yes
-Libraries: Yes
-Deployment: Don't really understand this one, but with Aegir and Acquia etc. I've never had a major deployment issue and I'm not even a sysadmin.
-Mobile: No? Does not seem to actually talk about the point. Could say "we're working on it", but really, I don't personally know the solution to this one.
Basically his arguments only applies if you start from the ground up. Which we don't.
Backwards compat problem: That's an actual issue. PHP needs to move towards non-compat versions. Not a big issue if you have standards though, which we do.
Cache: Solved through manual caching (Drupal, Joomla, or custom all work).
Drupal security vulnerabilities: Right, and we actually address the issues. The same can't be said of most CMS, because they don't have a strong community to point them out.
Terrible code: Completely wrong. My job is to make my code legible, and Drupal standards exist to help me do that. PHP code, written by beginners, is terrible, but it's not necessarily bad. You can write bad code in any language.
The Drupal community is far from fragmented. Perhaps PHP community not as strong as it used to be. Not My Problem (not sure who's problem this is). Fully ready to move on when it becomes my problem though, that is, when Frameworks/CMS written in other languages become more efficient and as flexible, which they're not imo.
Include files: True, but resolved through most every CMS.
In the end, completely refuses to discuss the issue as something else than "we have problems to solve", though the issues he mentions are already solved. What problems are still unresolved? Not mentioned. Does not give compelling reason to actually change language and give up all the work that has been done yet.
I know that it's probable that we'll move away from it (judging from past experience), I can't say I won't be using next year because I still have no reason to change. Nothing spells doom for PHP right now, so when it's doomed I'll move away but right now I don't even see big issues.
Also, I need PHP in a way because it's the only language with strong communities. I need strong communities to help me provide quality, affordable services to my clients. I wish I could move to any other thing, but right now I can't, because there's no other CMS or web site building app/machine/magic with a strong enough community (only contender is Joomla!, also PHP).
So please, do share your miracle solution that would allow me to do as much for my clients in the same time, with the same kind of support in case something goes awry.
Edit2: Also don't really get why you call PHP Cobol-esque, didn't see that in the vid.
4
4
u/Nextrix Jan 05 '11
Great, now we just need to wait for Views to get a 7 release.
1
u/superGreatAwesome Jan 05 '11
I thought it was supposed to be built into 7?
1
u/hlstd Jan 06 '11 edited Jan 06 '11
Views isn't included in Drupal 7 but I've been using the alpha (http://drupal.org/project/views) with great success and a release should be here soon.
Edit:views has been released. Less then two hours later.
1
u/superGreatAwesome Jan 06 '11
Awesome news. Coincidently I have a medium to large sized website project coming up in a few weeks that I was going to use Drupal for. I'm very familiar with 6 from previous projects. I'd like to use 7 though, would it be safe to use, in your opinion, this soon after release? I know in past drupal releases it was always rule of thumb to wait a few months for module devs to catch up.
1
u/Nextrix Jan 06 '11
No that is CCK that was built into Drupal 7. Merlinofchaos just pushed out an alpha release of Views for 7 today.
9
17
u/Cardinal_Sin Jan 05 '11
I love you Drupal
16
u/gormcito Jan 05 '11
Hey honestly, I'm really genuinely curious and I know this is going to make me sound like an ass, but I'm not trying to be. What is with all the "Drupal is amazing", "I love Drupal"? And if people are reading this and think I am just picking on one comment here, really go check out their forums and IRC, it's very common to see all this.
I've used it (version 6 that is), and while it isn't terrible I have a pretty "meh" opinion of it, I could complain about many things I encountered while developing modules for it, but that would be silly as I don't know if a perfect framework exists anywhere, but I certainly do not see it as a great piece of software.
5
u/mozillalives Jan 05 '11
I completely agree with you. I thought it was a little crazy when a friend told me Drupal was way better than anything he'd tried. I've used it for a couple of projects now and I have to say I agree, at least as a CMS solution.
The first thing is that the core is pretty well organized and the online documentation is nice. Building in your own functionality is well documented and you can do it through a well defined api (without mussing up the core). Same for themes. The second thing is something my friend likes to say, "there's always a module for that". Pretty much anything you would like to do with drupal has been done already and released as a module.
I still like things like django or kohana for personal projects but for putting together a CMS site in very little time, it's hard to beat Drupal + Views and CCK.
8
u/Shocker88 Jan 05 '11
The main reason is the community. It's honestly better and more helpful than the other CMS's around. Learning drupal as a developer is more difficult than basically any other CMS/framework, although the benefits once you have learnt it are great, without the community you'd have to give up at some point whilst only realising 2% of its potential.
3
Jan 05 '11
I would definitely say the community. It's an incredibly helpful and tight knit community.
I also think system is architected fairly well. There is definitely a very steep learning curve, but once you get over that and into the zen of drupal development, you can really pump out high quality sites fairly quickly.
→ More replies (1)3
u/alpha7158 Jan 05 '11
Different CMS's are more/less suitable for different projects. When I think of drupal I think of it as a content management framework rather than system. Great for large projects with many intertwined features that need to be pulled together. From a business perspective it allows for a much greater value for money end product to be created.
The community is great and there are a huge range of modules ready for the taking.
My 3 CMS's of choice are normally Drupal, ModX revolution and Wordpress depending on the nature of the site needed.
5
Jan 05 '11
I had a "meh" opinion of Drupal until we decided to use it for a project and I bought the Pro Drupal book. It's an incredibly good book describing an incredibly complex piece of PHP code and how everything ties together. Conclusion? I said "fuck this" and moved the project to Django.
Now I'm (literally) using the book to support my notebook stand. LOL.
10
u/poptartgod Jan 05 '11
So you evaluated a CMS, said fuck it, and moved to a framework, which involves a tremendous amount of extra work (in a completely different language too)? Drupal is not that difficult. I own all the Pro Drupal books and they're pretty straight forward. Plus the resources for Drupal development is much more abundant (podcasts, videos, meetup groups). It sounds like you gave Drupal half-assed consideration.
5
Jan 06 '11
I gave it a really long consideration. I actually read the whole Pro Drupal book, and that's why I know it's a really good book. I highly recommend to someone who is absolutely sure about using Drupal.
That said, Drupal didn't fit my needs. What we needed was something that'd rely heavily on a flexible document model (we were storing a range of survey-like forms) and the CCK just wouldn't cut it. Also, I realized most of the functionality I was going to be able to use (users, profiles, permissions, nice admin, etc.) would be a matter of hours, at worst days using Django, and I felt much more comfortable with Python.
5
u/Shocker88 Jan 05 '11 edited Jan 05 '11
I agree with you completely, however you are coming off as if saying learning drupal is a 10 second walk in the park - which in relative terms with the alternatives, it's the complete opposite.
As I said in another comment here the community and its resources are key to the learning process - thus the podcasts, videos and meetups. However one of the key issues with Drupal gaining popularity over the alternative CMS systems is considering how much time "considering" needs to go into the system they choose.
Wordpress isn't by far the most popular CMS choice because it's a haven for developers. It's freaking easy to use, looks simple and acts simple. Drupal 7 made some steps in the right directions but one of the key points made by key contributors is that the complexity of the system for a completely new developer can be overwhelming.
Anyway, basically just saying whilst innervision might not of put enough effort into drupal to see the benefits, we (as drupal users/community) cannot rely on new users having the time or patience to see the benefits when they can just get the job done with a simpler system such as wordpress, or to jump to a framework they know to actually begin being productive on a project. Learning Drupal straight up for a complex site would take so much learning that most people are likely to walk away thinking they'll never be able to work everything out. Even though overall time spent would be halved in Drupal, at least falling back to their familiar framework they are able to feel productive and know that the project can be completed at a reasonable pace.
edit: Sigh, sorry this is probably a post for drupal.org haha -_-
6
Jan 05 '11
My worst nightmare is that the Drupal community listens to everyone going on about how popular Wordpress is and tries to make Drupal more like it.
It would be like Apple and Google copying Nokia because Nokia phones are the most popular worldwide.
1
u/Shocker88 Jan 05 '11
Yeah good point. It's a hard balance between the two but I think both can be achieved - to an extent.
Obviously it can only be dumbed down so far as drupal is so complex currently and no one will let much of that complexity die as it kills features they want...
I guess it's mainly just about providing developers an easier entry into Drupal and its key advantages as most of the hostility towards Drupal is from code purists which think it offers no advantages to a standard framework and just bloats a system.
Obviously there's the potential for system bloat if people go crazy installing modules - but the extensibility and time that can be saved with these modules isn't understood properly. Obviously the key issue to learning drupal is the whole framework but I think its just about continuing to grow the community and ensuring people contribute back by sharing knowledge so people can find code examples in documentation/online on how to do things rather than bang their head against the learning curve :)
→ More replies (2)1
u/CritterM72800 Jan 05 '11
Same here, but I feel pretty sure that won't happen. There are always posts in the core issue queue about how Drupal can't do something that WP can do or how WP does something better, and most of the time the core devs just mark them won't fix and ignore them. There are rare cases where they take inspiration from WP's way of doing things (like installing and upgrading modules via the GUI in D7 - there was a lot of "this is how WP does it" in that issue), but I haven't seen it very often.
3
1
u/yesimahuman Jan 06 '11
To me it seems the only reason to use drupal is if you want non-technical people to contribute a lot of text content to your site easily. Other than that there is no way I would ever build an application on top of it.
Am I missing something? I've used drupal and extended it a bit but that was a long time ago and as soon as my love affair with php ended so did my time with Drupal.
2
0
u/Grantismo Jan 05 '11
I haven't used Drupal, but I've used the heaping pile of shit that is Fatwire. All I know is most cms are astronomically bad. If people actually celebrate a cms, it's got to be pretty amazing.
1
u/DrupalDev Jan 05 '11
To be fair, people will generally celebrate what they're already using instead of trying to look at other stuff.
I love Drupal and all but I've seen so much partisanship from all sides it's not even funny.
1
u/sintheta Jan 05 '11
What major benefits would drupal offer over wordpress? Assuming wordpress can be tailored to accomodate just about any site structure, I'm guessing drupal just offers this ability more natively?
→ More replies (2)2
u/AlejandroTheGreat Jan 05 '11
That assumption doesn't really hold for sites with more than a few contributors.
0
Jan 05 '11
[deleted]
3
u/exposur3 Jan 05 '11
Heh, exactly. I always tell people that if they haven't cursed Drupal, then they haven't spent enough time with it. :)
5
13
2
u/alpha7158 Jan 05 '11
I have a mid sized project to make soon and have spec'd a site out for Drupal 6.
I am unsure whether to jump to Drupal 7 for this hold back with 6 for now and use 7 after some time has passed. My concern is that the size of the extension library in Drupal 7 could be a stumbling block over 6 for the short term.
What do you guys think?
4
u/pertheusual Jan 05 '11
I guess that really depends on what modules you'd be using in the D6 version, and whether they have or will soon be having D7 ports.
1
u/ZoFreX Jan 06 '11
Same boat as you, site is sketched out in D6 and pencilled for end of Jan launch, not sure which to go with. Will probably stick with D6 for now, and learn D7 in a month or two so modules are more mature.
2
u/jutct Jan 05 '11
I can't wait to try it. The only problem will be the existence of a comprehensive knowledge database for D7. Without a good knowledge base, I would have never figured out D6
2
u/elvisliveson Jan 06 '11
..."much much more"
fuck that, explain the much much more. a bag of potato chips at the super also offers much much more..but everyone knows the bag is full of air.
"The problem with Drupal though is that you need to afford a person or team to deal with it." - nuff said.
2
4
Jan 05 '11
I love Drupal but I'm not really a fan of the new admin in modal windows approach. I know this might sound insane but I've tried many different CMS and Forum scripts and the best admin interface by far is vbulletin. Even though it uses frames, or used to anyway.
9
u/whoisrich Jan 05 '11
I found the new floating toolbar admin really annoying.
Was happy to find that going into Modules and uninstalling 'overlay' and 'toolbar' gets rid of it.
3
3
Jan 05 '11
I thought the same at first... but then I realized that site owners are going to love it. Admin interfaces scare clients.
3
u/DrupalDev Jan 05 '11 edited Jan 05 '11
More job for me!
By the way, our very own /r/drupal is pretty nice.
-1
Jan 06 '11
Specializing in Drupal right now seems like specializing in CGI web development in the late 90s.
Hint: No one uses CGI anymore.2
u/DrupalDev Jan 06 '11
So you can tell the future, eh?
In any case, I'm not too worried, if (when) something better comes up I'll jump on the bandwagon. I think it's a given that if you're going to work in web dev you have to keep your eyes open for the next good thing.
1
u/diuge Jan 06 '11
So, in your opinion, noting better has come up to replace Drupal?
1
u/DrupalDev Jan 06 '11
Not for what I'm doing, which is to say, affordable websites. I don't know of any Django or other CMS-based workplace in the area (maybe I didn't look hard enough because I love my job, will remember to do that).
2
1
u/shatteredmindofbob Jan 05 '11
Drupal scares me. But I suppose that's why non-developers shouldn't be playing with CMS backends...
1
u/spundnix32 Jan 06 '11
Ok so I have never used drupal. Should I try it with 7 or just wait?
1
u/silvercircle Jan 06 '11
You could wait for Drupal 8, since it will probably be even better than 7.
1
u/jn2 Jan 06 '11
Drupal 7 is great, but with anything new, there may be some bugs to work out. Download it, give it a try, watch for updates. I really love the new interface.
0
0
u/midri Jan 05 '11
I really feel like drupal is a great example of the average php programmers way of thinking... Why has no one built a robust cms ontop of cakephp that's gotten popular? Cakephp is the closest you can get to developing on rails for PHP (which is a good thing) It's always on my list of things to do but I get sidetracked with shit that makes me $...
3
u/mirzu Jan 05 '11
Simple answer: Drupal predates Cake, and it's popularity and community are what make it so powerful. A quick google search turns up a plethora of CMS solutions built on top of Cake, but none of them have the install base, the module collection or the community of Drupal.
It's not as elegent as Ruby or CAKE or Grails, but what you gain in existing functionality makes up for some of the frustration and head scratching.
3
u/CritterM72800 Jan 05 '11
drupal is a great example of the average php programmers way of thinking
Would like to see examples so that we can refute them.
25
u/UnConeD Jan 05 '11 edited Jan 06 '11
Despite being a "content management framework", the core doesn't actually save you from writing code. You still have to write CRUD code, still have to manage validation, still have to define your own themables. That is, unless you use CCK/Views, which is pretty much developer-hostile lasagna and slow to boot. And it'll look like ass, unless you have an ubertalented designer who also knows PHP (i.e. a "themer", a role which doesn't exist elsewhere). And the one part that you would actually want to contextualize, i.e. the content UI, is shoehorned into the node/edit form with zero choice.
Despite the promises of the hook system, Drupal lacks the ability to swap out components. If you wish to leverage part of the page generation process for another purpose, you have to reimplement everything that comes after. Alter hooks are terrible tools for building reliable behavior, since they require you to actively fight against other parts of the system instead of just turning them off. If you don't share Drupal's assumptions about user accounts, you're fucked, unless you feel like trapping and erasing UI messages is a productive use of your time. And don't even try to maintain the resulting code.
Despite being billed as having a "solid core", Drupal's irreplaceable innards are actually pretty fragile. Form API is near impossible to debug and fails silently at the drop of a hat. The node system doesn't even let you reliably do programmatic saves. The user system is a terrible misdesign that mixes front-end presentation details ($category) with low level data manipulation. The global $user object is actually a useless fake, waiting to trip you up.
Entire portions of Drupal were created in a theoretical vacuum and released without any serious working implementations. For example, install profiles: they are executed in an incomplete pseudo-Drupal environment where it's actually impossible to do certain simple things due to static caches and dysfunctional APIs. Another example: Form API process functions with complex datatypes and dynamic AJAX manipulation. Theoretically possible, practically a nightmare.
The problem can be summarized quite effectively: out of the box, it is impossible to make a slick, modern website with Drupal, i.e. something that looks and feels like 2011 rather than 2001. It's only useful if you're already planning to write a lot of custom PHP/HTML/CSS. Otherwise you have to be happy with terribly designed contrib components that are insecure, don't scale and have bad usability. This is not surprising since Drupal has been in incremental-improvements-mode since 2002 (i.e. Drupal 4.0) and the few architectural improvements made since then were designed with only one purpose in mind: to support what Drupal already does, rather than being solid components of a CMF.
Doing Drupal will stunt you as a developer, overburden you as a designer and frustrate you as a user.
waves
5
u/Ergomane Jan 06 '11
and frustrate you as a user.
... and core developer
5
u/CritterM72800 Jan 06 '11
For those wondering, UnConeD is Steven Wittens, the 10th person to ever register on Drupal.org and a former core committer (of which there are very very few). He had a huge impact on Drupal core development until somewhere around 3 years ago, when he left.
3
u/the_exa_boy Jan 06 '11
Not surprised, ive had my run-ins with the code team.
1
u/Ergomane Jan 06 '11
Mind telling us where? Can't see anything that I'd describe as 'run-in' on your tracker.
→ More replies (2)2
5
u/davereid20 Jan 06 '11
Steven, we appreciate your early work to Drupal which helped shape the community and software. But this just comes off as bitter remarks from someone who is no longer involved rather than an honest critical review. Step up and help us fix things we can fix. File issues. Come to DrupalCon Chicago and hash it out with us.
1
u/UnConeD Jan 06 '11
I have only listed real world issues that I encounter daily in my job. And like the Drupal community always does, the only reply you'll get if you point out structural problems is "well, we fixed that one minor thing, so your entire criticism is invalid".
The state of Drupal today is a logical consequence of the core reviewing process: it is always easier to lazily argue for the status quo than for a change. Unfortunately, people assume there is some inherent value in the way things work today, without actually caring what the original assumptions were or if they are still valid. There is also an inherent flaw in the reviewing process, which, in the long term, favors badly written contributions (which cause lots of discussion and review, hence awareness) over solid ones (which get committed and then forgotten about). People are happy if their contribution makes it in at all, and then wash their hands of it out of frustration. Rinse and repeat for 7 years, and you have a hundred reasons not to come to DrupalCon.
3
u/Crell Jan 06 '11
Steven,
You're absolutely right in much of your criticism. The way nodes save is utterly broken, and has been for at least 5 years. The user module is a laughing stock, and has been for at least 5 years. Hooks are good for what they're useful for, but they are NOT a plugin mechanism by any stretch of the imagination. They're an extension mechanism only. We utterly lack a plugin mechanism in core; instead we have about 8 that are all slightly different.
All of those pieces of code have been in Drupal for years, dating back to the early days of Drupal before most current core contributors were even in the project. That is from the era when you were an active core committer.
Your issues with the review process (in the immediate parent to this comment) are also largely valid. Even as a subsystem maintainer I can't get a straight answer on if I have any more influence on a patch than someone else, and I've been asking for 3 years. We actively recruit the "casual weekend hacker" type contributor and mindset and coding style, thereby alienating professional software engineers every way we can. It also alienates designers and other non-hackers: http://www.disambiguity.com/drupal-7-and-beyond
This is a review process that evolved in Drupal's first half of life, back when you were an active core committer.
I want to see these issues addressed. It will be hard, very hard, but there's a growing number of people who disagree with the status quo of "quantity over quality" and "enough eyes are a substitute for good planning and expertise". People who want to see the node save system not suck, and having a real plugin system that's not just a mis-used language hack.
These wheels are moving. Slowly, but they are. It is not easy at all. But there are hundreds of people who are desperate for the kind of changes you're talking about, and to address the shortcomings you point out. And having a formerly active core committer involved would help immensely in making those kind of changes happen.
And that is a hundred reasons that people SHOULD come to DrupalCon...
9
u/CritterM72800 Jan 06 '11 edited Jan 06 '11
Hey, it's Steven! Thanks for that. Here are a few responses:
unless you use CCK/Views
That is pretty much a given. In fact, CCK is even part of core in D7. Commenting on Drupal sans-CCK/Views is sort of like commenting on a car without its tires (bad analogy, I know).
which is pretty much developer-hostile lasagna and slow to boot
The first part is vague and the second part screams for benchmarks.
And it'll look like ass, unless you have an ubertalented designer who also knows PHP
Is this really so different than every other system? WP requires themers know PHP to do anything useful in a theme. ExpressionEngine uses its templating system which is basically just a different looking version of PHP. I'd be interested to see what you think is so different about Drupal here.
And the one part that you would actually want to contextualize, i.e. the content UI, is shoehorned into the node/edit form with zero choice.
Not really sure what you mean here, but if you're just saying that it's difficult to customize the node's output, then you might checkout the contemplate or display suite modules.
Despite the promises of the hook system, Drupal lacks the ability to swap out components. If you wish to leverage part of the page generation process for another purpose, you have to reimplement everything that comes after.
This is a legit point.
Alter hooks are terrible tools for building reliable behavior, since they require you to actively fight against other parts of the system instead of just turning them off.
What's the difference? You can turn things off with alter hooks. What's an example of a system that has a preferable behavior here in regards to overriding core behavior?
Form API is near impossible to debug and fails silently at the drop of a hat.
This is just an opinion. I've never had much trouble with FAPI.
The node system doesn't even let you reliably do programmatic saves.
Same as above; I've never had trouble with node_load() and node_save().
The user system is a terrible misdesign that mixes front-end presentation details ($category) with low level data manipulation.
This sounds like a nitpick to me. Does this really affect your programming or make any difference in your day to day work? Or does it just bother you on principle?
The global $user object is actually a useless fake, waiting to trip you up.
I'd be interested in more details here too. For example, it's fairly common to grab the uid from global $user, and I've never really hard any complaints about global $user before now.
install profiles: they are executed in an incomplete pseudo-Drupal environment where it's actually impossible to do certain simple things due to static caches and dysfunctional APIs.
Certain things like what? I only have a small amount of experience with install profiles, so this is a curiosity question.
Form API process functions with complex datatypes and dynamic AJAX manipulation. Theoretically possible, practically a nightmare.
I'll agree here. That said, D7 has made some huge strides in improving the AJAX DX.
out of the box, it is impossible to make a slick, modern website with Drupal, i.e. something that looks and feels like 2011 rather than 2001. It's only useful if you're already planning to write a lot of custom PHP/HTML/CSS.
By "out of the box" do you mean without any contrib modules? If so, then I'd agree, but that's sort of beside the point. You're supposed to take advantage of contrib modules, that's sort of the beauty of Drupal. And as for requiring a lot of PHP/HTML/CSS, I'd say that HTML/CSS is pretty commonplace in any CMS, and the PHP really just depends on the use case (you can do many many crazy things with Drupal/contrib modules without any custom code at all).
Thanks for that well thought out and well written post. It's well to see such a well reasoned critique of anything, including Drupal.
7
u/UnConeD Jan 06 '11 edited Jan 06 '11
That is pretty much a given. In fact, CCK is even part of core in D7. Commenting on Drupal sans-CCK/Views is sort of like commenting on a car without its tires (bad analogy, I know).
CCK is only good if the UI provided by CCK suffices. If it doesn't, then the added hassle of having to deal with procedurally generated objects, types and tables quickly becomes a nightmare. I've found it much, much easier to just write a simple ORM mapper and do the rest myself, and not for lack of trying either.
It's not just me who goes without it: the Ægir hostmaster system that stores all its data in node types also chooses not to use CCK. Go look at the people who made that and tell me they don't know Drupal.
Incidentally, you're talking to UID 10 on Drupal.org. Long story.
The first part is vague and the second part screams for benchmarks.
You must be unaware of the layers of indirection that are taking place here. Also, views is terrible on the inside. It's a nightmare of handlers, plug-ins and uncaught errors waiting to happen. There's also the fact that using Views requires you to structure your code very differently and in a remarkably un-drupal-like way. For example, you cannot ship views templates inside an associated module's directory (unlike regular templates), they have to go in a theme. Unless you implement hook_theme_registry_alter() to undo it, yay.
Other people apparently feel the same.
My latest Views project was trying to hook up an external data source to Views 3. It's absolutely terrible and that's with example code to model it off (apachesolr).
Is this really so different than every other system? WP requires themers know PHP to do anything useful in a theme. ExpressionEngine uses its templating system which is basically just a different looking version of PHP. I'd be interested to see what you think is so different about Drupal here.
How do I get rid of the colon after form field labels? The answer is not to tweak a template of HTML-with-sprinkles but to dive into hardcore PHP code. Shall we mention theme('table')? Or perhaps the $node->content array of doom?
Not really sure what you mean here, but if you're just saying that it's difficult to customize the node's output, then you might checkout the contemplate or display suite modules.
Actually I meant the node editing form. It's the most basic part of a CMS, and Drupal sucks at it. Vertical tabs or not, the idea that everyone should edit all sorts of content through the exact same UI is madness. It also ignores the fact that you don't create an end-user oriented UI by hiding parts of the developer-oriented UI and calling it a day.
What's the difference? You can turn things off with alter hooks. What's an example of a system that has a preferable behavior here in regards to overriding core behavior?
The proper answer is to use inheritance to override behaviour rather than to undo it, e.g. using MVC to separate concerns and OO to allow for selective code modification.
Go and try to make it so that people can log-in with their e-mail address instead of their username. I'll wait while you figure out how to get rid of the error messages that no longer make sense.
Or perhaps you would like to replace the godawful password recovery page with one that actually looks like something a real web service might use? Unfortunately, the code that verifies the security hash is intricately tied with the part that displays the UI so your only option is to menu_alter out the entire page and reimplement it.
This is just an opinion. I've never had much trouble with FAPI.
Have you ever defined a custom element type? Used #after_build or #process functions? Used #ahah/#ajax? And done so without ever encountering a random type error deep inside form.inc? The menu system suffers from the same affliction: if you accidentally forget the array() around the 'access arguments' for example, you'll end up with some cryptic error deep inside menu.inc. The only way to debug these errors is to insert trapping code at the reported location, which incidentally is a whole cache refresh and page request later than the offending bug.
Fact is, Form API is undocumented and untested for the things it was supposedly designed to do. Do you know the rules around form caching and $form_state['storage']? When $form['#cache'] is needed? Or that your form element IDs will get broken if you trigger a form rebuild inside a page request? Yay. Still broken as far as I know.
Same as above; I've never had trouble with node_load() and node_save().
Detailed here: http://www.reddit.com/r/programming/comments/ewoub/drupal_7_released/c1bl1cl
This sounds like a nitpick to me. Does this really affect your programming or make any difference in your day to day work? Or does it just bother you on principle?
Have you looked at the signature for user_save()? You cannot simultaneously modify two properties that are situated on different user profile tabs. By design. If you do any work with hook_user(), this will bite you in the ass. User objects are also unique in Drupal in that they will store custom properties for free. Incidentally, this has lead to many contrib modules polluting the users table because they don't expect it. Like the legal.module, which pushed the entire terms of service into every single row in the table.
I'd be interested in more details here too. For example, it's fairly common to grab the uid from global $user, and I've never really hard any complaints about global $user before now.
Passing the global $user object into user_save() will result in data loss if you have any modules that extend the user object. Simple as that.
Certain things like what? I only have a small amount of experience with install profiles, so this is a curiosity question.
Just one example. There are many, because of how much of a clusterfuck install.inc is. It tricks Drupal into thinking it's already installed to bootstrap it, and then pretends nothing's wrong when it installs all your modules and themes (which then fails when they do anything complicated on install).
You're supposed to take advantage of contrib modules, that's sort of the beauty of Drupal.
Except for the part where they are insecure and have terrible usability. Like for example the Single Sign-On module, an authentication module that let you steal UID 1 access from an admin with a single click. Or the Services module, where an elaborate fix for a reported security issue was itself insecure and spoofable. If you look at the security reports for Contrib, you find that they are the same vulnerabilities over and over again, in different modules, over several years. People are not writing better modules.
I have yet to encounter a situation where I can actually drop in a contrib module and have it satisfy my professional requirements. It just doesn't happen. I have to review their security, fix the interaction flow, get a designer to make it actually nice... and that's assuming there isn't some DB-server-destroying query in there.
If I have to audit every single contrib module I want to use, and the reward is a module that's kinda crappy anyway, I'll pass. It's just not worth it.
2
u/CritterM72800 Jan 06 '11 edited Jan 06 '11
Incidentally, you're talking to UID 10 on Drupal.org. Long story.
Yeah, sorry about that. Right after I posted, I realized it was you. I wouldn't have dumbed it down if I had. Anyways, thanks for the replies.
1
u/vertice Jan 06 '11
I get your point, but Ægir is nothing like your typical Drupal site, and the typical best practices don't and shouldn't apply to that specific of an implementation.
Our reasons were maintainability, deployability and dependability.
I actually wouldnt recommend the use of CCK for anything other than prototyping, because it becomes nigh on impossible to provide a reliable upgrade path, even if you follow best practices
And no, i'm not fond of fields in d7 either.
2
u/davereid20 Jan 06 '11
"How do I get rid of the colon after form field labels?"
Gone by default in D7.
→ More replies (4)1
u/CritterM72800 Jan 06 '11
Short on time, but just a few quick responses.
Ægir hostmaster system that stores all its data in node types also chooses not to use CCK. Go look at the people who made that and tell me they don't know Drupal.
I get your point, but Ægir is nothing like your typical Drupal site, and the typical best practices don't and shouldn't apply to that specific of an implementation.
How do I get rid of the colon after form field labels? The answer is not to tweak a template of HTML-with-sprinkles but to dive into hardcore PHP code. Shall we mention theme('table')? Or perhaps the $node->content array of doom?
You're picking out the bad parts and ignoring the good parts. Every system has seemingly simple things that end up being complicated, Drupal is no different.
the idea that everyone should edit all sorts of content through the exact same UI is madness.
It may be, but it's the standard. WP, Django, ExpressionEngine, Joomla, all have a one-size-fits-all content-editing UI.
Or perhaps you would like to replace the godawful password recovery page with one that actually looks like something a real web service might use?
Why can't this be done by theming/blocks/whatever? What exactly would you want to do to that page that isn't easy?
Except for the part where they are insecure and have terrible usability.
This is a risk you take when you use community code. Again, it's no different in WP plugins, EE modules/extensions, etc. In fact, I've found the quality in Drupal to be above par.
I have yet to encounter a situation where I can actually drop in a contrib module and have it satisfy my professional requirements.
If that's true (never? really? not even the tiny do-almost-nothing modules?) then your standards are irregularly high, and hundreds of thousands of sites have been built by devs who used contrib modules and didn't feel the same, yet had no major issues.
3
u/mikey_p5151 Jan 06 '11
As I responded to the comment below, I'll just save a few point for here. I don't know how much you've been following Drupal 7, but this really reads like a laundry list of complaints of issues that have been addressed since you were working on Drupal.
I'm not even going to take the time to go over where I think you're wrong and which issues have been fixed. I'm sure you think that anyone that still uses Drupal has their head in a microwave, but complaining about the problems that were there in the releases you worked on instead of discussing the fact that people stuck around to fix many of them, is just poor taste.
Doing Drupal will stunt you as a developer, overburden you as a designer and frustrate you as a user.
This should read: "Doing any single (framework|cms|platform) will stunt you as a developer
2
3
u/dlundy Jan 06 '11
Get out of my head.
Just about everything you've said here is what led me to quit a job writing reasonably complex stuff in Drupal. I could never articulate it this well, though.
I will admit that there is a certain sweet spot where Drupal can be helpful and productive, but if your codebase morphs into something outside of Drupal's comfort zone, then all I can say is good luck.
3
3
Jan 06 '11
You are my new god. You've succinctly put to words everything I've been feeling over the past few years I've had a Drupal project on my plate.
1
Jan 06 '11
Wow really really well written. I've got to save this for future reference. Those are all pretty major shortcomings of Drupal. The most frustrating is getting rid of the stock UI. That crap always finds a way to seep into your design.
Can you clarify what you mean about the node system not letting you do programmatic saves? Or was the key word 'reliably'? If so yeah I'd have to concur.
3
u/UnConeD Jan 06 '11
The problem is really the node_form and how it shapes the code around it. The idea is that you take the entire $node, you turn it into a $form structure with fields, which is then shown to the user. Then the submitted form values are serialized back into a new $node (which is made secure through Form API access control on fields).
This is dumb, because it elevates the form fields from just a UI implementation aspect into meaningful structure. It also means you need a comprehensive bidirectional translation scheme between $node and $form, which in practice means people get lazy and make forms that look like airplane cockpits.
But where it gets really problematic is that many contrib modules (out of ignorance) don't even bother translating back from $form to $node, and hardcore their node_save() callbacks to accept only the $form values. Passing in a vanilla $node will simply not work and result in data loss, aggravated by silent failure and those crazy type casts PHP is famous for.
I actually made a flowchart of this process for Drupal 6 to explain this to a coworker: http://acko.net/dumpx/why-drupal-nodes-suck.pdf
As far as I'm aware, the only way this has changed in 7 is that the $form fields are now automagically combined with the original $node, so that values not present in the $form are not lost. But otherwise, module authors are still expected to grasp MVC-related concepts in a system that has neither the vocabulary nor the grammar to express these ideas fluently.
5
u/mikey_p5151 Jan 06 '11 edited Jan 06 '11
While this does perfectly describe the problems with previous versions of Drupal, I think quite a bit has changed since you have been around and committing. Any entity that properly implements field_attach_* hooks has a consistent data structure that can be loaded, modified in place, and saved without concern over whether the $form fields match the structure that the saving function (and ultimately field_attach_insert and field_attach_update) expect. It just works. Seamlessly.
As to mapping form field to entity fields, of course that will never match and any system that claims to integrate those items ends up being what Drupal was, not what it is now. field_attach_form and field_attach_form_submit are what glues these two items in a default way, but keeps the data structure of the object 100% separate from the values of the form itself. I'd suggest anyone that has fought this code in the past, write their own entity module that is fieldable, and use these functions to understand how they actually work and how the data structures work.
But where it gets really problematic is that many contrib modules (out of ignorance) don't even bother translating back from $form to $node, and hardcore their node_save() callbacks to accept only the $form values.
This is just silly. We aren't talking about 4.7 and 5.x contrib modules. We're talking about Drupal core, and it's changed alot. Not to mention nothing prevented users from writing Drupal 5.x or 6.x modules that DID NOT have this problem. Project module (for all it's cruft) actually does an awesome job of putting it's metadata in consistent, repeatable, and sane places that work whether it's getting a form value or a $node object.
Nothing is stopping (other than lack of time and motivation) fixing the node preview issue once and for all, the object I get back from field_attach_form_submit() has all the fields in the exact same place they are when they are returned by entity_load() and field_attach_load().
6
u/UnConeD Jan 06 '11
I've actually dug through quite a lot of D7 code. And noticed all the "Fix this in D8" comments that show the issues I've raised are still there.
Besides, you're focusing on the minor complaints and ignoring the big ones I started out with. But since you insist, take a look at node.pages.inc:90-99 ($node being stateful, in direct contradiction with how Form API is designed) and session.inc:106-127 (global $user is a fake) and tell me these are the hallmarks of a well-designed system. None of these things matter for vanilla stuff, it only comes out when you try to push the system into more advanced ways of interaction. You know, doing experimental development, pushing the edge, what Drupal used to pride itself on?
As for core vs contrib...as the rest of this thread shows, you can't look at Drupal core in isolation. In practice, the vast majority of people do rely on contrib modules, and Drupal.org does not make any effort to suggest doing otherwise. It is dishonest to pretend that the ultra strict principles of Drupal core, which only arise as a result of a strict vetting process, will spontaneously radiate outward to contrib modules and the sites that use them. It has never happened, and it won't change any time soon.
As for your accusations about "poor taste"... I'm posting technical arguments in response to a direct challenge about Drupal weaknesses, on a site that isn't Drupal.org. If that somehow offends you, tough luck.
→ More replies (1)2
Jan 06 '11
Thanks for the awesome flow chart and info. I've got to ask about one more thing you've brought up. I've long suspected the global $user object to be a bit, well, suspect. Though it hasn't bitten me in the ass yet, I feel like I'm just waiting for the other show to drop as our program gets more and more complex. Could you elaborate on any known problems or is there anything I should keep in mind when coding to save myself some sanity in regards to $user in the future?
2
u/silvercircle Jan 06 '11
Pre-Drupal-7, global $user is not fully loaded. See the description here
2
Jan 06 '11
Much appreciated. So Drupal 7 introduces a robust caching system for $user kind of like with $node now?
2
u/davereid20 Jan 06 '11
That issue has nothing to do with the global $user object. It's still not a full-loaded user.
2
u/chu Jan 07 '11 edited Jan 07 '11
But otherwise, module authors are still expected to grasp MVC-related concepts in a system that has neither the vocabulary nor the grammar to express these ideas fluently.
It's no problem to do that kind of pseudo-MVC (as used in most web frameworks) in Drupal as it's effectively Hierarchical MVC/PAC in any case. Rich models containing all business rules implemented OO in include(s) with a clean API (able to use complex data structures, unlike being tied to an ActiveRecord-based framework), module/menu as controller/router, template files as view - job done. Nice part is that you get AOP baked right through into the bargain. Architecturally it's a hybrid but that doesn't make it a bad design.
1
u/fago Jan 06 '11
I'm with you, the node form workflow was a mess. However, the good news is that for d7 it got fixed to actually work as you describe in the pdf it should! :)
1
u/chu Jan 07 '11 edited Jan 07 '11
Disagree with your summary, having been involved in modern big sites with near zero code required. (Though obviously you are going to write full HTML/CSS on any serious site, otherwise there's WP.)
You have clearly identified in detail coding/design issues that you find problematic on a project where you were a major contributor. Have you moved onto a different framework that you think is better and somebody had already done this work? And why not tell us about this better alternative instead of just 'Drupal sucks'? The issue list you have compiled is clearly useful for anyone working on Drupal 8 architecture in particular, but I'm sure you're aware that it's not usually a problem to find a contributor to talk about why any framework x sucks (though maybe not so much in a public forum) as they are intimately familiar with all the expediencies and inconsistencies that were required to create useful software in a useful timeframe. I've heard similar tales of WTF-ness (albeit it lower level like those frameworks) from Zend and Rails camps for example. (I've also seen Drupal do far more complex integrations far more easily than other frameworks.)
2
u/UnConeD Jan 07 '11
Why speak up? Because people should know what they're getting into. If Drupal works for you, great. But Drupal folks need to realize they are at the center of a giant reality distortion field that conveniently papers over its flaws in favor of an almost cultish feel-good vibe. It's a huge community, arguably the biggest OS community in the world, and what comes out is a product that is meh and doesn't look like anything that is exciting on the web today.
There's also the fact that I've observed these processes at work up close, for years, and don't believe Drupal will change any time soon.
But it's not like I'm on some crusade to discredit Drupal. I've barely written anything about it since I left. I merely saw an opportunity to speak up and did so. Given the response, it seems like it was a good idea.
2
u/chu Jan 07 '11 edited Jan 07 '11
Drupal folks need to realize they are at the center of a giant reality distortion field that conveniently papers over its flaws
I think it's unfair to say that Drupal papers over its flaws. The issue queues and IRC are full of contributors quite vocally recognising and working on these issues. Patches are picked over in detail from the POV of code and design quality. Of course there are still design issues and bugs, some persistent - just like any other large software project. This is all in public and available for anyone to see - how could it be 'papered over'?
Yes, the community markets Drupal, on the implicit understanding that widespread implementation is the path to long-term software survival and improvement - again like any other software project.
And if you want to talk about reality distortion fields, where to begin? Maybe first take a look at Rails or Agile (or the enterprise Java world for that matter). Regardless of any hype, there are still functional sites written in Rails, and Agile continues to usefully break barriers between business and dev. Applying Occam's razor, could it not be that people gush about Drupal because it actually solves their problems? Despite its reputation for weak usability, I've repeatedly had excellent feedback from business users who don' care what the underlying technology is.
what comes out is a product that is meh and doesn't look like anything that is exciting on the web today
You haven't offered a better alternative - what do you think is exciting on the web today? You've just said that the Drupal community is unable to produce quality software and held up some design imperfections as evidence. From a business perspective, Drupal leads the field in its class and is a no-brainer for many commercial websites both small and at scale. That is one definition of quality software. And then there's the more technically exciting stuff - MongoDB support, RDFa, OAuth and services, an ECA Rules engine, fieldable entities, pluggable auth and caching, l10n/i18n, external services piped through Views. (You say you tried the last and found it painful to get working, me too - but I believe that's completely expected for any cutting edge development, particularly AOP-based. And to be fair Views 3 has only recently gone into alpha.)
You say you want to warn people - then surely give a balanced view and also consider the strengths and weaknesses of the alternatives.
2
u/fewpeople Jan 05 '11 edited Jan 05 '11
I don't know why you are getting downvoted, my sentiments exactly. IF you want power/functionality, then you probably need to customize, so why not just build it via Cake or some other MVC framework. IF you want simple and basic, choose wordpress which does a lot of the CMS tasks Drupal does, but makes things like ADDING AN IMAGE to a page simple.
Edit *"does a lot of the CMS tasks" rather than "90%"
3
u/Shocker88 Jan 05 '11 edited Jan 05 '11
Until the "choose wordpress which does 90% of what Drupal does" I was in agreeance.
But unfortunately you're going to have to take this downvote for being completely misguided. I'd have been in agreeance if you had of said "choose wordpress which provides the CMS functionality". But saying Wordpress can do 90% of what Drupal can is completely incorrect. Yes Wordpress as a basic CMS (changing content from an end user perspective and adding a widget here and there) is great, but for much better extensibility you need Drupal, it's already providing the framework and CMS you're talking about trying to custom code/workout multiple systems to provide a solution for you
In the end its at the developers discretion for what they choose to develop within, however after the initial headache of learning how everything works within drupal - it does provide the solution both of you have been discussing in a much easier packaged and quick system. It's not always the answer, but it's rarely not a good answer.
edit: Probably should link to prove my point on the 90% being well off the mark - check drupals core API here
→ More replies (5)1
u/fewpeople Jan 05 '11 edited Jan 05 '11
IMO, the point of a CMS is for the End-user to focus on content, and in my experience, unless they are forced to do so (or they are technical), they won't learn the complex usability that Drupal has going on. Thus it FAILS at it's initial task.
Also, I don't get why you'd learn the quirks for a specific system, than to just learn a framework which you can apply in general anywhere. Wordpress for basic sites --> Cake/MVC frameworks for everything else.
5
u/Shocker88 Jan 05 '11 edited Jan 05 '11
Because once you understand Drupal it's about as quick as putting together a simple site as Wordpress and it cuts a TONNE of custom work out of most larger projects that you'd be throwing Cake/MVC frameworks at. Plus it's much easier learning and teaching all of your companies employees one system rather than 2+.
Drupal is essentially both a framework and a CMS integrated into a single package. Rather than custom code a CMS up for each site you do (or even code up a stock standard one) it's already there and easily extensible through content types and views.
There are some times where you'd want to move to a framework system - but Drupal with its contributed modules and CMS functionality can literally cut 3/4 of a heavy development project out by providing the solution for it in a structured and stable approach.
Drupal can be used in basically anything thrown at you given the knowledge and thus learning its quirks of it is beneficial as it's likely you won't need to move outside of it as a framework.
Cake is a great and very clean framework, however it can't cut as much time out of a project as Drupal does. (I havent used it in a few years - however seems there are no solid supported CMS options yet). My move to drupal was a forced one by my current employer. Would never have switched otherwise as it just sempt dirty from the outside.
Once you can get your head around Drupal I assure you there's little places you wish you were able to use another framework and/or CMS.
2
u/AlejandroTheGreat Jan 05 '11
It's also much better for your clients to leave them a working site that they can hire someone else to maintain. A from-scratch site will make the poor bastard coming after you who has to grok your whole codebase want to burn your house down.
1
u/boombatta Jan 05 '11
I can sorta see what you mean when comparing Drupal to Wordpress, but as I see things, if you develop your Drupal site well, create specific roles for those who will be maintaining the site, and keep the end-user in mind as you develop (creating meaningful vocabularies, fields, etc), then I don't really see there being issues due to an overly complex usability and maintainability. And I've developed for some extraordinarily untechnical people. But I don't mean to take anything away, I think Wordpress is brilliant. Cake though, I never liked, but I know I'm in the minority on that one. :)
1
u/skillet-thief Jan 05 '11
It isn't like it is impossible to write a CMS with Cakephp. But it seems like the whole point of Cake is that it is for rapidly building applications that are much more flexible than most CMSes. Once you go the CMS route, you might as well get a big boxed kit.
1
u/midri Jan 05 '11
I suppose that's true. I've been apart of many projects that tryied to make a cms ontop of cakephp but they all fall apart when the elected group leader starts wanting to implement to high level stuff...
1
u/Bjorn2404 Jan 06 '11
Expression Engine is built on CodeIgniter. It's not free (but a pretty fair price) and I haven't tried it but I really need to check it out one of these days. There is a community but I don't think it's nearly as big as Drupal's.
1
u/midri Jan 06 '11
The idea of paying for anything with so many excellent free alternatives blows my mind.
2
u/Bjorn2404 Jan 06 '11
When you work on websites that have budgets in the tens of thousands to hundreds of thousands, a couple hundred dollars or more for a quality product is never out of the question.
1
u/dominatrixyummy Jan 05 '11
Another thread about Drupal, another bunch of flamers. Who would have thought?
-2
u/HIB0U Jan 06 '11
Pointing out the thousands upon thousands of flaws in PHP and Drupal is not "flaming". It's a technical analysis that unfortunately reflects very poorly on the target technologies, mainly because they're piles of shit.
-5
u/gdr Jan 05 '11
/programming instead of /webdev is a common typo, you are forgiven posting this
6
u/bananahead Jan 05 '11
Just wait... I think these new fangled "Web-based applications" are really going to catch on.
1
u/gdr Jan 08 '11
This belongs to programming as much as announcement about new release of MS Office because it allows you to publish documents and extend itself.
0
Jan 06 '11
Haha, people who know PHP and the adobe suite think that they are programmers. It's cute, kinda.
-3
u/o2pb Jan 05 '11
Ohh great. Now my 8 core 16GB ram machine can deliver even less page views per day without being overloaded by this bloat-ware!
4
u/AlejandroTheGreat Jan 05 '11
If you aren't just trolling I'll point you to the Pressflow distribution - it integrates a lot of the available performance enhancements that Four Kitchens and others have developed for Drupal.
2
1
u/Shocker88 Jan 05 '11
You sound like someones got a knife at your back to upgrade ASAP to the "bloat-ware"?
-4
-8
Jan 05 '11
I'll stick with Wordpress, thanks.
7
u/mozillalives Jan 05 '11
Until recently I thought the same thing. But I tried 6 with the Views and CCK modules and I was really impressed with the flexibility. From a user perspective, I still think the wordpress admin is awesome. Slick and easy to use for any noob. But even if it takes a little more user training with drupal, I would rather go with it just because of the features.
4
u/Shocker88 Jan 05 '11
Glad to hear you took the plunge. It's a long learning curve that'll keep going but it only means things get better and better :). Views and CCK are staples but once you start integrating CCK with Ubercart and/or custom node setups you begin to find the true power ;)
3
u/boombatta Jan 05 '11
Ubercart especially is pretty sweet. You can really get a lot of nice e-commerce functionality going pretty quickly.
1
Jan 06 '11
In my line of work I need to be able to easily instruct clients on how to use the interface that their site is built upon, but for more complex projects I suppose I should give it a shot.
Is there a healthier Drupal theming community nowadays?
1
u/mozillalives Jan 06 '11
It seemed good to me but I kinda cheated - a friend of mine helped me get started. His suggestion was to work from the Zen theme (which you can do by extending it - you create a subtheme that inherits from the parent) and use the Zenophile module to quickly start the subtheme (no need to figure out what files to copy or settings to create). From there I simply looked up whatever I needed in the documentation.
0
0
u/edwardlkerr Jan 06 '11
Starting with a team that is strong in Drupal, $500k can go a lot farther than starting from scratch. Have you looked at the core API? That's a lot of code I wouldn't want to write from scratch.
-2
u/grandwazzoo Jan 05 '11
Well, yeah. At least I'm paid to update and maintain this unusable piece of crap.
-3
u/IndianGuy79 Jan 06 '11
I own drupals.com - what should I do with it?
Any ideas? I can run it for moderate traffic ADS-FREE as long as my hosting provider doesn't kick me out
1
u/TheBreeze Jan 07 '11
You could just run a drupal install... oh wait it's probably a shared host. You're going to need a lot more RAM.
-15
0
Jan 05 '11
[deleted]
5
u/bananahead Jan 05 '11
Drupal is as good a starting point as any. It's a good framework for beginners because there is a very active and helpful developer community.
3
u/midri Jan 05 '11
If you know PHP to some degree already I recommend Cakephp -- it has a lot of the power that ruby on rails has (ActiveRecord) and also follows MVC (Model/View/Control) which makes projects of any scale a lot more sane to work on. You do have to program a bit more, but with a bit of foresight you can design your sites to be fairly modular and take pieces from one or the other later on to speed up your development time. + Cake has an active and thriving community with loads of plugins.
20
u/[deleted] Jan 05 '11 edited Jan 05 '11
BTW, if anyone wants free beer and to hang out with nerds.. check out http://www.drupal7releaseparty.org/
Currently 267 parties in 91 countries planned.
edit: I should say free beer in many, but not all, cases :)