2 ms·
What do you mean when you write "a custom content application loses to Drupal on all 3 of the above points"? Consider this: http://www.indeed.com/jobtrends?q=d
by lkrubner 11y ago
What do you mean when you write "a custom content application loses to Drupal on all 3 of the above points"? Consider this:
http://www.indeed.com/jobtrends?q=drupal%2C+node%2C+rails&l= http://www.indeed.com/jobtrends?q=drupal%2C+node%2C+rails&l=
There is a lot of custom work in the Enterprise. It dwarfs any one CMS.
Also, about #2 in particular, do you think it is hard to find Node talent or Rails talent? They both seem fairly abundant to me.
Regarding #1, I'm sure you can recognize this as a double-edged sword:
"You can buy enterprise software support from Acquia."
That is the problem, the Enterprise support is associated with a single company. Unlike, say, Rails development, or especially Java development, where there are a zillion companies selling to the Enterprise.
The problem for Drupal is in trying to find that space between "too big for off-the-shelf" and "too small for customized solution". It's a very narrow space.
- snowwrestler 11y agoWhat I should have said above is that Drupal is a more narrowly defined product than Rails or Node or other frameworks. Drupal 8 is moving toward a "framework" approach, but it's still just a "web content management framework." So for the people who just need to manage web content, Drupal will have the advantages I list above. It's more a matter of being better fit for a particular purpose, than some inherent superiority of technology. For building software products in general, including in-house enterprise products, Node, Rails, and others will still be winners. But for managing web content, Drupal comes with enough functionality, security, and developer support out of the box that it will beat custom solutions a lot of the time.