SuzyUK - 8:16 pm on Apr 26, 2009 (gmt 0)

I test for module_exists before taking action, then I should be able to turn modules on and off without breaking the site.

and that is a prime example, I do not hack core, have never done so - I as a themer *should* have no interest in if a module exists or not. However not all modules are created equal, sometimes you turn them on and a site design breaks. I with my themer hat on has to be aware that this can happen in order to create a somewhat robust solution (release a theme)

a case in point: I've recently found a fault with Views that would bounce back to a designer, or many contrib themes

Personally, I've already taken control of my own designs/themes, no matter the modules being used, through my .info file, but until D6 who knew or knows how to do that.

RE:OP

Some people say it is by default ugly, but sites like TheOnion, MTV UK, et al look pretty good to me.

It is ugly by default, and those sites have people working on their theme constantly. Likely teams who are proficient at both PHP and CSS. Those themes are not OS (nor should they be) which I think is reason enough to question what Drupal is not good at. If Drupal is to go to the masses then this layer has to become easier.

[edited by: SuzyUK at 8:45 pm (utc) on April 26, 2009]