[development] development Digest, Vol 106, Issue 18

[Ernst Plüss]

Well this depends A LOT on the requirements your enterprise
application has (and is of topic of this mailing list).

Just my two cents:
#1 If there is a system that does most of what you need. And you can
add/adjust it to what you need - great. Just to give an example: If
you have to deal with a lot of users generating different kinds of
content and you need a solid and extensible shop solution, Drupal is
your friend. If you want to blog, Drupal is fine but maybe looking at
Wordpress isn't a bad idea.
#2 If your problem domain is to specific you need a system that helps
you to concentrate on the business you have to solve and not on
technical issues. CakePHP, Ruby on Rails (with Hobo), Grails are
things to look at here.
#3 If you are looking for some thing more mature (but requiring much
more work) look at Java (Wicket2, JBoss Seam, GWT, ...) or .Net.

HTH



2011/10/21 Darren Douglas Lee <darrendouglas.lee at gmail.com>:
> On 21 October 2011 11:41, <development-request at drupal.org> wrote:
>>
>> There are systems which let you doe
>> this with much less work.
>
> @Ernst - Can you provide a list of the "systems" you're pointing to?
>
>