On Jun 15, 11:43 am, Torsten Bronger <bron...@physik.rwth-aachen.de> wrote:
> First you need a functional specification for your project, > i.e. "must have"'s and "nice to have"'s. Size and agility of the > community as well as documentation are important, too. Then you can > filter a little bit. But most established frameworks/CMSes will > still fit the bill. It depends what your "zoom level" is. For example, the org's questions may be questions like: - In which system can we get our site up the fastest? - Which system will be the most flexible if we need to go in new directions? - In which system will it be easiest to find qualified developers? - In which system can I mix and match data models to our heart's content? - Which system has the most mature 3rd-party plugins/modules/apps? - Which system's templates are easiest to work with? - Which system will make it easiest to convert our existing data into? - How easy is it to create custom workflows? These are real-world questions that apply equally to frameworks and CMSs. > The primary filter must be the language anyway. The people who are The counter-argument is that languages are similar enough that experienced / good developers can get up to speed pretty quickly even if you change languages. In other words I'd rather work with an experienced/good developer even if it means they have to learn a new language than to work with a less-experienced developer for whom learning a new language is a deal-breaker. My .02 ./s -- You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-us...@googlegroups.com. To unsubscribe from this group, send email to django-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-users?hl=en.
