> > The concerns are few:
> - lack of big corporate backing (like Seam) and guaranteed sound > documentation Lack of big corporate backing is seen as an advantage to some. They need to make money somehow and support contracts can be very lucrative. Small teams can do amazing work. Just look at what the Django people have accomplished. - much smaller user-base than RoR I hadn't noticed. Django is certainly smaller than Java EE. Python appears to have a lot more choices for web frameworks than Ruby. RoR does have mind-share right now and is probably a viable alternative to Python and Django but I like the Python language better. - possible future extension of the project with a procurement system > and resulting demand on resources The immediate thing I would look at is if the procurement system only provides an EJB interface or some other Big Vendor lock-in. Sometimes that barrier can be crossed but it could be painful. The last is not an immediate concern and the scale is not yet clear. > The speed of development is much more of a concern. Speed of development definitely points to a dynamic language. Good luck on your project. Take time to play with several options before you settle and see what works for you. This is a Django joint so I'd gently push you in that direction. Then again, you won't find me hanging out with my Java brethren if that means anything to you. In the end its your choice. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~----------~----~----~----~------~----~------~--~---
