1) Drupal is not suitable if you want to create anything that hasn’t been created before. In other words, it’s not useful if you are creating something of value. Drupal fanboys reply to criticisms that it’s too complicated by insisting that it’s too powerful and flexible for the person who says so. Unfortunately, Drupal fails here even more than it fails in simplicity. The tiniest change can require tapping into core and that means having to repeat yourself when an upgrade comes.

Unless vanilla Drupal, plus CORE modules are sufficient for you, best make something from scratch. It will be easier in the long run, even if you factor in the time required to make your code secure (which isn’t as hard as people insist it is). I’ve had a few really good Drupal programmers concede this point to me. I’ve been told it’s my fault for “having too many customizations.” Nothing of value is going to be off the shelf and if off the shelf is sufficient for you, then something easier to use like Joomla or Wordpress or Concrete 5 would be a better choice.

2) The community. People who’s livelihood rests on wielding this one hammer (Drupal) against all the screws, pieces of pressboard and antique china the internet has to offer. They insist that everything is possible in Drupal. It’s their mantra, but all that really means is anything is possible in PHP (not really, but I’d let that less preposterous claim slide). There’s great hostility to creativity, wanting to do things in a way that is user-friendly or attractive or using non-standard ajax or javascript. I met quite a few Drupal coders I liked, don’t get me wrong, but asking if anyone has had experience doing something in Drupal on the forums always resulted in “why would you want to do that?” Drupal makes sense only to Drupal developers and are hostile to all criticism, even if it’s valid and constructive. (I’ve seen quite a few non-derogatory posts get deleted that should’ve have been).

Rails is better. MIT license. Or roll out your own PHP CMS using Zend. Or use Django. Or join the Concrete5 community and help them improve their damn good CMS. Or if it’s simple enough, use Wordpress (fun to make plugins for). You can’t make your own web apps in Drupal (I think many Drupal programmers would admit that, but countless Drupal users insist you can and will waste your money trying to make it for you and failing miserably).

However, the biggest reason I think people get frustrated with Drupal is NOT that it’s hard to learn or anything of that kind. In fact, I think it’s EASY to do certain things with Drupal quickly. The hard part is building a site you want exactly the way you want and that seems to require a lot of customization within the framework. The unified administration interface of Drupal makes that a lot harder.

To me, getting a unique community website is about putting several components together and making them seem part of the whole deal: blogs, articles, reviews, news updates, forums, albums, galleries etc. Thing is most CMSes try to unify all these aspects into one solution. Most of them end up being complex and bloated and Drupal seems to be no exception to that rule. As a result, it makes it harder to build something out of a CMS that actually looks UNIQUE and DIFFERENT. Of all the time I spent tweaking around with Drupal, I never felt that I could make it fit into my needs with lesser effort. It seems I was fighting the software to make it work the way I want it. In the end, I figured that the added effort was not worth it.

As an analogy, I’d say Drupal is a wild beast that requires a lot of taming and controlling before you can get it to dance to your tunes. Whether it’s worth it or not depends on your own requirements and patience.

Wordpress is the best alternative to drupal. It has it’s own internal problems with spaghetti code, but at least there’s much less code to deal with and it’s a bit easier to understand the internals, mainly because there is less code. Besides, wordpress looks nice, works great, and is easy to learn right out of the box. It’s also a piece of cake to convert it from a blogging app to a straightforward CMS.

If you’re going to end up even looking at the code (and you will have to by necessity if you use Droople or Rails), you may as well just save yourself some time and just change a few lines of wordpress code and just get on with your life.

http://www.graphicdesignblog.co.uk/wordpress-as-a-cms-content-management-system/

http://www.noupe.com/wordpress/powerful-cms-using-wordpress.html

The flaws being there are very few “awesome” modules in Drupal, even realtively popular ones have bugs open for weeks or months, they are generally bloated because they try to please everyone and the popular frameworks all have many plugins, modules, libraries, etc that also solve a problem for you.

DRUPAL ROCKS !

This illustrates how far off-base many Drupal fans are. A large number of vulnerabilities IS NOT a measure of good security and Drupal DOES NOT do a better job of publishing or releasing updates than other OSS projects. But it is not all Drupal’s fault. PHP is a good part if the problem, not being OO, it doesn’t compile, is dynamically typed, and very easy to write sloppy code…

While Drupal certainly isn’t the worst OSS out there the criticism mentioned in this blog post are all valid and they are all good points (unlike most of the rebuttals).

Also, if you look at some of their functions it gets more retarded, for example:


4.6 – 5 -user_authenticate($name, $pass)
6 - user_authenticate($form_values = array())
7 -user_authenticate($name, $password)


It gets pretty retarded between versions, somebody thought it would be a good idea to change the function parameters in 6 and 7, and change it back to the normal usage. This simple example screams bad development all over.

I’ll stick with Ruby on Rails and not Drupal with seven cups of coffee.