The drop is always movingYou know that saying about standing on the shoulders of giants? Drupal is standing on a huge pile of midgetsAll content management systems suck, Drupal just happens to suck less.Popular open source software is more secure than unpopular open source software, because insecure software becomes unpopular fast. [That doesn't happen for proprietary software.]Drupal makes sandwiches happen.There is a module for that

Yes, this is Drupal, not WordPress

Submitted by nk on Fri, 2007-11-16 08:09

On Drupal Planet, one of the first things I saw this morning was a quote from my answers to factoryjoe's review. The author of that blog post easily skipped the fact that it was me who copied this review to infrastructure to make discussion easier and spent considerable time to review and answer. My answers was just, asking for implementation where I saw something great and turning down others. Often the latter complained about too many options to which I succintly repied that we are Drupal, not Wordpress -- Drupal has many features -- and yet, simple UI is needed but a simple UI is not taking away the options, see next paragraph. Also the author already forgot that we picked the same IXR library for XML-RPC as WordPress did and the decision to do this in 2005 was influenced by WP's pick. Guess who did the port to Drupal.

Drupal is willing to learn from whatever project, but the "too many options are bad" philosophy we can not adapt. Just this morning I worked with webchick on adding a way to add a vocabulary / term simple and quick while keeping our powerful and flexible "advanced" forms, too. So, yes: we are Drupal, not WordPress but we are willing to learn.

Commenting on this Story is closed.

Submitted by on Fri, 2007-11-16 14:45.

Drupal's many options are good. I guess too many visible options are bad. Or perhaps: too many concurrently visible options are bad. So that's what we have to work on.

Submitted by amyStephen on Fri, 2007-11-16 15:10.

Language discussions always make me chuckle. There is no right or wrong way to portray these things. 25 years in the industry and thousands of discussions on standards and word choice and process - is there any other subject people get *more* passionate about? It certainly appears that there is a direct correlation between passion and a lack of serious involvement in the work. Goodness! Talk is cheap!

Now, step back for a moment and consider how most people cannot grasp technical discussions underway between developers. As a result, many end up standing on the sidelines, feeling uninvolved. When a discussion on language opens up, people jump in and participate.

Looking closely at the article, your statements were taken out of context. I had not paid close enough attention because, first of all, I was very busy yesterday, but, to be honest, I do not care about language discussions that much. So, my sincere apologies. I should have said something to the author when I read it. My initial thought was, Eek!, I don't disclose developer discussions in blogs (see my response to the author for more on that), but, it's sometimes a fine line I walk when encouraging people to openly participate and censoring. ? I don't always do the right thing.

Please remember, though, given who you are, people pay attention to what you say. Sadly, they won't always understand, and they won't always be careful, some just want an opportunity to participate in the debate so that they feel more involved in this amazing project. As Drupal continues to gain popularity, these types of miscommunications will also increase. :P

But, people wanting to get involved is a good thing and, it is a positive statement about the impact of work you and others developers have contributed to make Drupal what it is today.

Stay encouraged. You are an obvious important, influential and positive contributor to open source. Your efforts are much appreciated by thousands and thousands of people. Imagine the reach of your good work!
Amy :)

Submitted by on Fri, 2007-11-16 18:06.

I completely agree with this. I love the "many" options both for development and for the CMS interface.

I think most people need to create the "admin" user (uid 1) and then create the "manager" user (uid N) and give manager what ever rights they _need_ and never log in with the admin user again.

Because of the nature of user_access returning TRUE for uid 1 always, there will _always_ be a s#!%load of options available and this is overwhelming to the average user. However if we have a blogger profile that creates two initial users, a user user and an admin user and recommend they use the system with the user user, I think we would see less complaints about "too many options".

my $0.02


Submitted by stephthegeek@dr... on Fri, 2007-11-16 21:25.

Totally agree. Too often our clients browse their sites as administrators or editors, not what 99% of their users would actually see.

Submitted by on Sat, 2007-11-17 06:54.

Chx, my reply via my site as to why I saw the quote from the OSC article had merit for Planet Drupal. I felt my reply was too long to post here but you're welcomed to cut/paste it here if you would rather not redirect traffic back to my site. I'm definitely not in it for the traffic...

Submitted by timmillwood@dru... on Tue, 2008-09-02 09:15.

Drupal needs to be able to compete with Wordpress and therefore needs to offer the same feautres and more. I don't think these features have to be core. So what is needed is a Drupal wordpress clone install profile.

Which links nicely to my discussion on "is Drupal too general?"