Re:Australian government likely to standardise on Drupal
by noir_lord on Saturday May 10, 2014 @11:59AM
(#7725846)
I'm not really sure how to respond to that since we are in the realm of personal opinion.
I've built custom CMS's for clients that where a much closer fit with their existing workflows that implemented most of the list above (not everyone requires everything above) and I've done it at least as quickly as doing it from scratch in Drupal would have (partially because I have existing code I can reuse for a lot of that).
My visceral dislike of Drupal comes from working with it directly for two years, I read the books, I went through the code, I wrote custom modules, I learnt CCK/Views inside and out and at the end of it I took a pay cut to not have to work with Drupal.
My opinion of Drupal can best be summed up with an analogy - given sufficient thrust even a brick will fly and Drupal required a vast amount of thrust.
Yes out the box you get a great deal of functionality which is what makes it so enticing but then your needs change and you require doing something that is outside the scope of Drupal or even existing modules and the whole thing comes crashing down.
Back when I worked with Drupal it created hundreds of tables for anything involving slightly complicated CCK/View based workflows, performance was horrible for logged in users (and trust me I haunted 2bits like a poltergeist for every tuning opportunity I could find).
But then this is just opinion at the end of the day.
One thing I will say is that the Drupal community are an absolutely lovely bunch and incredibly helpful which is always a strong plus.
I've built custom CMS's for clients that where a much closer fit with their existing workflows that implemented most of the list above (not everyone requires everything above) and I've done it at least as quickly as doing it from scratch in Drupal would have (partially because I have existing code I can reuse for a lot of that).
My visceral dislike of Drupal comes from working with it directly for two years, I read the books, I went through the code, I wrote custom modules, I learnt CCK/Views inside and out and at the end of it I took a pay cut to not have to work with Drupal.
My opinion of Drupal can best be summed up with an analogy - given sufficient thrust even a brick will fly and Drupal required a vast amount of thrust.
Yes out the box you get a great deal of functionality which is what makes it so enticing but then your needs change and you require doing something that is outside the scope of Drupal or even existing modules and the whole thing comes crashing down.
Back when I worked with Drupal it created hundreds of tables for anything involving slightly complicated CCK/View based workflows, performance was horrible for logged in users (and trust me I haunted 2bits like a poltergeist for every tuning opportunity I could find).
But then this is just opinion at the end of the day.
One thing I will say is that the Drupal community are an absolutely lovely bunch and incredibly helpful which is always a strong plus.
Also just for humour value http://www.cmscritic.com/wp-content/uploads/2010/08/permissi... this is not a good UI.