Hallöchen!
shacker writes:
> [...]
>
> These comparisons are not only possible, they're essential for a
> boss or a company trying to decide on their next platform. Only us
> geeks say things like "They can't be compared." Of course they
> can.
Well, somewhat.
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.
The primary filter must be the language anyway. The people who are
supposed to work on it must feel comfortable with it. If they do,
they'll work as efficient with any mature tool.
But you can't compare further technical things like "this ORM layer
may be better" or "that wiki-in-5-minutes screencast is more
impressive". The worst thing are benchmarks. Never look at them.
Tschö,
Torsten.
--
Torsten Bronger, aquisgrana, europa vetus
Jabber ID: torsten.bron...@jabber.rwth-aachen.de
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 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.
