1. Drupal versioning and support.
2. Plugin and themes dependency
3. Upgrade process.

If you have to stick with PHP, use PIMCORE or roll your own with Zend.

Typo3 is a pig. Don’t try to use it unless you have a lot of serious resources. Joomla is a bad joke. A total nightmare. Wordpress is fine for a blog (if you don’t mind being pwned), but a bad idea for a complex site. Use blog software for blogs, not for other kinds of sites. CMS Made Simple was headed in the right direction, but then they ditched their “let’s re-architect this like sane people” 2.0 project, and most of the best people have left the building. If they sold stock, I’d short it. Does anyone seriously look at projects like MODx or Website Baker? If so, they need help.

Then I rolled about laughing and stopped reading.

Well, this guy is using Wordpress, which is used to power thousands of blogs these days. I don’t blame on them. Many people have money to hire a developer to even create a “widget” showing past 10 comments which are posted today.
Also, you could pay someone else to manage something small.

Drupal is not a magic. It’s well-thought coding.
DRUPAL ROCKS!

First, you have to understand that if a CMS is fixing security issues, that’s good. Drupal does not charge you for security updates so why don’t this guy see the good side? Okay. Wordpress is now 3.X.X…. Typically these X.X versions don’t have major updates. So these X.X updates(minor updates) are just for either security fixes or bugs in core. The, why don’t you say WORDPRESS SUCKS ? Please be logical.
Also, nobody publish active security issues in latest version. If someone noticed or experienced security issues, they can securely inform to security team, there is an active, dedicated team for that.

Also, don’t think that Drupal is just a tarball which has all the functions out-of-the-box. You can’t build any good site without Views, CCK, Token and other few modules. How do you say is it okay to use core but not modules? If then, Drupal could create “magic-Drupal.tar.gz” package and include all 7789(to the date) modules in it, which costs 3 Gb of size, and you may need to update it daily. Funny ?
Understand the practical situation. In your own blog, don’t you use Akismet or any third party module ….. I got the word – “third party!”. Then, you say Drupal is “First party” ?

I’m not blaming anyone here, but these guys don’t understand basic theory.
If you don’t kn0w HTML, CMS is NOT the solution. Find a good online site building site or something like site-reptile, etc. Do not use CMS without understanding what is it.

Also, this blogger prioritize “piss” instead of Drupal. Also he/she don’t know what is a “View” at least. Views should be in the database because it’s coding. “View” just store a set of instructions to display certain things such “last 10 comments today”. Haven’t you used phpmyadmin’s views ?

>>WIB: Best practices dictate using a version control tool like Subversion or Git which, among other things, lets two developers “download” the same code so they can work on it simultaneously. Unfortunately for Drupal developers, database settings are not typically stored in version control. This means that two developers have no easy way of coordinating their work. Further, it means you’ll have a heck of a time replicating your settings across multiple servers if you have a high-traffic site that requires load balancing, or a staging server where you want to preview changes before they go live.
—– hahaha…. Does wordpress developers work on a code stored in a database ?
Don’t make me laugh, please. Database is just for data.

>>Logs record visits to your website, together with other useful details like errors. When you get lots of traffic, logs tend to get huge – we’re talking gigs. Logs are important for debugging, but, unless you’re a high-security outfit, they do not need to be permanently stored. If you back up your database regularly – and you should – you’ll be transferring all that unnecessary data every time you run a backup. Further, you might want to grant a sysadmin or programmer access to your logs to help diagnose a problem. You don’t want that person digging around in your database for this information: one bad search query and your data is gone.
—– If database logging is the problem, yoiu could set a limit or disable “database logging” module.(Drupal also support syslog which logs events to server itself.

You say you have to go to adminster > content management > content to edit an existing blog post. Are you blind ? Can’t you see “edit” link above the blog post ? To edit all posts, you have to go there. Do you suggest Drupal developers to put all links in one single menu level ?

Is Drupal searfch sucks ? Simply go to drupal.org and search for something. you will get neat results in few mili seconds. please don’t be point-less.

Thanks a lot for pissing. Please find a good place.

The first time I Googled for an answer — my crime had been not knowing what to make of a bizarre error that flooded my screen after I installed a module — I found a thread on my subject. Unfortunately, the thread consisted of:

Q: “Hey, guys, I got this error.”
A: “Everyone else could figure it out, why not you?”

Also, the apologetics for not using Object-Oriented Programming are nothing short of hilarious. Every now and then someone comes by to say, “hey, guys, why don’t we turn our plugins into objects, like in Wordpress?” and the hostile reaction is:

1. If you think we need object-oriented programming, you just don’t understand the architecture of Drupal!
2. Even though it’s not object-oriented, if you think about it, the way Drupal as whole works is OO
3. But that doesn’t matter because OO would be bad
4. Even if it wasn’t bad it was not available in PHP 4 so shut your mouth.

I used to use Drupal a few years back, before I had been introduced to these other frameworks and tools. I thought it was the bees knees, you can install these modules and override just about everything. But when I started working with other platforms I quickly changed my mind.

Drupal takes the worst aspects of a framework and combines them with the worst aspects of a CMS. Configuration is a huge pain in the ass, since it’s stored in the database. It’s generally hard to use and slow. The api is very procedural and ugly.
The queries for your content will usually do over 5 or 6 joins, which is horrendously slow.

Drupal is for people who want to build a whole website by clicking buttons. You could say it is the Dreamweaver of the CMS world. Developers are far better off using a framework where your work is done with clean code. If you use version control this is a huge win. Maybe if you’re not a developer it will be good for you because of this. However it is not a tool any professional should ever use.

Django or Silverstripe introduced me to clean object relational mapping, classes, simple templating (Drupal templates are very hard) and scaffolding. I prefer Django, because python is far superior to PHP, and the community is much larger. However silverstripe is both a great CMS and framework for content driven websites. To be honest I think Silverstripe stole a few ideas of Django. In either of these frameworks one just quickly write some fields into a model class and have the administration backend generate the forms and navigation to manage the content. Compare that with clicking 20 times to make your CCK model in Drupal.

Django, Rails, C# .NET are all used for large *dynamic* websites. Just because the white house puts up a news site they cache the shit out of doesn’t mean Drupal is a good solution. Also, PHP sucks balls. It’s 2011, move on from this legacy language. Until the Drupal fanboys have given the alternatives a try they should STFU.