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.
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.
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...
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.