8
u/Ergomane Jan 06 '11
From one of the Drupal founders (from http://www.reddit.com/r/programming/comments/ewoub/drupal_7_released/c1bkf7o ):
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
2
u/valdemar81 Jan 06 '11
the core doesn't actually save you from writing code. [...] That is, unless you use CCK/Views, which is pretty much developer-hostile lasagna
Right, if you don't use the systems designed to save you from writing code, then you won't be saved from writing code. If you don't like the lack of perfect flexibility, then write your own code. There's no magic solution that builds a perfect solution by reading your mind.
2
u/mikey_p5151 Jan 06 '11
I've responded in the other thread. I've never seen Steven referred to as a co-founder. 'Course given is bitter attitude towards the Drupal community I wouldn't be surprised if someone editing things in a hope of moving the project on, which is what it has done since Steven was around. As far as I can see, his last commit to Drupal itself was in 2007, about halfway through the Drupal 6 development cycle, so while he may have lots of perspective on where Drupal was, I don't think he's in tune with where it is now.
3
u/silvercircle Jan 06 '11
I would probably put Steven in the top 10 of all the programmers I know. A code review from him (if you could get it) was worth its weight in gold.
2
u/CritterM72800 mcrittenden Jan 06 '11 edited Jan 06 '11
And a good reply by mikey_p. Note that Steven (UnConeD) has been long gone from Drupal for years now.
EDIT: And another.
3
u/grumpypants_mcnallen Jan 05 '11
I still remember the botched 5 to 6 period. Amazing how they wanted people to use 6 but simple stuff like image field support didn't exist. Not into the internals of 7 but are all the major modules really up to par with their version 6 editions?
7
u/CritterM72800 mcrittenden Jan 05 '11
Simple answer is no.
More complicated answer: a LOT of the major modules are now integrated in with core, such as CCK, filefield, imagefield, imagecache, better_formats, jquery_ui, and a few others, so all of those are obviously ready. But of those that weren't integrated, it's hit and miss. Views, for example, is still in heavy development for D7.
3
3
Jan 05 '11 edited Jan 05 '11
I'm still fairly green to Drupal but my colleague is very much into it and has shown me all of the ins and outs. It's absolutely one of the best systems I've used. Being the WordPress I welcome the new interface overhauls, as well as the integration of new things into the core. I'm still getting the hang of 6 but I want to mess with 7 more.
Edit: "Being the WordPress fan that I am...". Whoops!
4
2
u/erode Jan 05 '11
I'm completely new to Drupal (been with Wordpress for a while) so I'm interested in learning more about Drupal 7 as that's what I'll be using.
1
u/narcissus921 Jan 05 '11
And all 38 pages of bugs. Sooooo looking forward to this. Just 2 critical bugs, plus a slew of others.
Oh wait, they're working on D8 already..
0
Jan 05 '11
[deleted]
3
u/CritterM72800 mcrittenden Jan 05 '11
Stuff like the new upper-right corner tabs (where you found perms) will definitely take a bit of getting used to, but all things considered, I find that almost all of the changes make more sense than how they previously were. I had just gotten used to the old way so I had stopped thinking about how illogical everything was laid out.
As for the overlay, there's also a per-user setting on your account page (see http://drupal.org/node/659480 if you're interested in the patch/discussion on that for some reason).
5
u/[deleted] Jan 05 '11
I'm still gonna hold out for a while and see how stable and secure it is before I put it on my servers but its good news.