Reply to comment

Hi Phil, Thanks for your comment. Well I can definitly understand you when you say that for non-tech user Drupal is certainly more difficult to understand. But for new users http://api.drupal.org is definitly not a place for start - new developer that want to learn Drupal should first check http://drupal.org/contributors-guide and also http://drupal.org/theme-guide, and off course purchase Pro Drupal Development book :)). api.drupal.org is just reference of all functions in drupal core modules. So yes for developer Drupal is probably more difficult to grasp then EE, but when you master it you can control everything in it and easily extent it to everything you need. I think EE is excellent in CMS domain; core Drupal install is very good CMS but you need to install community modules to bring it to EE CMS functionality, but with Drupal you can do much more then that - Drupal is actually Web Application Framework, and CMS is just one part of it. That is one of the main reason I chose Drupal - because it is excellent framework for developing web applications, and been PHP programmer that is exactly what I need :) And I am not worried that some important module will be depreciated. Actually all very important module (like Views, CCK, Panels, Organic groups, ...) are also supported by main Drupal developers, they just not follow same release cycle like core part. Also with Acquia now supporting Drupal in enterprise domain that can't happen any more - for example take a look at their Carbon project - this will be custom drupal distribution that will include all critical community modules and also many more - so basically all important modules that are not in core distro will be supported. Sure other modules that are not supported can become depreciated, but you always have a choice - if your business depends on that module you can hack it code and update it to latest Drupal version or hire developer to do it for you. I didn't visit EE forums so I don't know is support better than on Drupal forums. But you are probably right - in the end EE has employers which job is to provide support to users over forum, and Drupal don't have that. But that will also change with Acquia - one of their mission is to offer commercial support for Drupal. I just don't understand part where you say that code is EE in more clearer then using Drupal View module - sure if you want to grasp 100% of View module power knowing of PHP will help, but for most other situation you will not write single line of code, you just create new view from web admin interface and thats all, you don't have to be programmer for that. Both systems are very good, and as I said earlier it is really mater of taste and also mater of your business requirements - for my work i need excellent CMS but also clean, modular and future rich web application framework and Drupal is right choice for that.