Reply content:
1. How much you know about Drupal. If you do not understand the development of Drupal, did not accumulate, no guidance, decisively give up.
2, the project is expected. If the complexity of the business logic between the entity is very high, the process is very long, can not be implemented by the rule, give up decisively.
3, most of the powerful module is not used. Drupal itself is powerful, is to provide a set of good module mechanism, the real good place is its third-party module implementation, so if a lot of popular modules in your project is not used at all, decisively give up.
4, the strength of the team. Front end, you have to be able to use good zen-grid+sass, design best can meet 960grid,module development and understand ctools and views, panels and so on mainstream module integration, these talents are few. If, 3 of the 2 conditions are not satisfied, please give up decisively. One is a CMS, a PHP framework, you ask the wrong way, there is no comparability. I want to say that Drupal itself is the PHP framework. I think it's better to be familiar with Drupal than to rubyonrails development. Drupal is a high-end atmosphere, but it's hard to hold, and all the benefits of Drupal don't make any sense to you. Looks like, looked upstairs the answer, basic on a principle, you are not familiar with Drupal, the complexity of the project, Drupal is not suitable for developers who are not familiar with his agile development, learning steep, template and other tedious to do what you do best, Drupal is not so easy to get started
Drupal allows for rapid development. Drupal is a good choice if you want to quickly prototype a product.
Drupal itself is a PHP framework. Ruby on Rails is still in an unstable period, not updating a large version is incompatible with the previous one, so wait until it doesn't change.
