On the evaluation page, it seems someone copied most of Joomla’s points for Drupal.

Eg: Q: What is the worst thing about your web CMS?

Joomla
– Getting it to work and scale on the University’s preferred Sun/Oracle platforms and support procedures.
– Its newness causing there to be less support for it than the older version.
– Too many functions are enabled via workflow but workflow is very non intuitive and due to sheer amount of tech support calls we have to turn it off.
– patching and upgrades
– limited in design unless you have a designer who knows php.
– With Plone, difficult to teach the way plone/zope work – not nearly as intuitive as joomla, probably others, but the payoff with plone is huge, especially for a large site.
– departmental implementations with no central campus tool available.
– development interface sucks, big time

Drupal
– fairly steep learning curve for technical staff
– learning curve for development; too rapid upgrade cycle.
– Getting it to work and scale on the University’s preferred Sun/Oracle platforms and support procedures.
– Its newness causing there to be less support for it than the older version.
– Too many functions are enabled via workflow but workflow is very non intuitive and due to sheer amount of tech support calls we have to turn it off.
– patching and upgrades
– limited in design unless you have a designer who knows php.
– With Plone, difficult to teach the way plone/zope work – not nearly as intuitive as joomla, probably others, but the payoff with plone is huge, especially for a large site.
– departmental implementations with no central campus tool available.
– development interface sucks, big time