Hallöchen! shacker writes:
> On Jun 15, 11:43 am, Torsten Bronger <[email protected]> > 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. Absolutely, yes. But nobody will be able to give you answers to these, even if they claim they are. Take the template system (TS) as an example: Fans of TS 1 will say that TS 2 is over-complicated and hard to maintain. But fans of TS 2 will code faster in it than in TS 1. We are talking about mature systems only, so you can code efficiently in any of them if you abandon prejudices and fears of contacts. >> 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. In my experience it takes a long time before you master a language so that you can write maintainable code in it. It's a lot more than just writing working code. You must know the idioms and anti-idioms that the language's community has acquired over the years. And you must know the libraries, which are huge for today's languages. I'd never choose Scala for example, because you don't get developers with Scala experience. It may be a great language, but I'd prefer Python/Java/C#/Ruby/PHP and pick from a lot of applicants with experience in them. (Even Python was not so simple in our case, by the way.) Tschö, Torsten. -- Torsten Bronger, aquisgrana, europa vetus Jabber ID: [email protected] or http://bronger-jmp.appspot.com -- You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to [email protected]. 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.
