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

Just how big we are?

Submitted by nk on Fri, 2010-01-15 13:55

Up until now, Drupal tried (and tried hard) to work with every nick-and-dime shared hosting companies. We have changed course with the launch (and the success) of the GoPHP5 movement allowing us to use PHP 5.2 in Drupal 7. But that required a movement and was a huge change. I would believe that by now Drupal is large enough that it can set up some smaller requirements instead of worrying about which host will and which won't support it. One such has long been a problem -- the memory requirements -- but this as a problem affecting everyone and is filed and worked on as a critical bug. Instead, I am talking of certain PHP extensions. It would simplify Drupal code a lot if we could be sure that SQLite is always available so the install/update/maintenance code does not need to do special dances. Maybe we could make cURL a requirement as well to have a capable browser all the time. Let's have these in Drupal 8 -- we are big enough now that no sane hoster would want to say "no, we are not compatible with Drupal".

Commenting on this Story is closed.

Submitted by WorldFallz (not verified) on Fri, 2010-01-15 14:51.

I wish it were so-- unfortunately I think you severely underestimate the arrogance and greed of the hosting industry. Not to mention the user base, who even now, insists they should be able able to run a full production site on www.somecrappyfreehost.com with no issues and actually post indignantly to the forums when they can't. :-(