[Ilugc] [JOB]Opportunities for Python Developers/ Web application developers
- From: lawgon@xxxxxxxxxxxxxxx (Kenneth Gonsalves)
- Date: Wed Jan 30 12:48:35 2008
On 30-Jan-08, at 11:55 AM, Vamsee Kanakala wrote:
I would say the activity of a project is a better way to judge such
stuff - in which case, TG hardly seems to be 'dead in the water' -
the latest commit being on Jan 21st. There ought to be more
objective reasons for that kind of statement.
when i was choosing between rails, tg and django in 2005, I joined
all three IRC channels. There were 45 on tg, 45 on django and 400 on
rails. Today tg has 45, django has 340 and rails has 290. As for
sites and resources for django -
http://code.djangoproject.com/wiki/
DjangoResources and
http://djangosites.org - nothing comparable on
tg. If you check the mailing lists also you will find the same sort
of proportion. If you look at the number of contributors of code you
find django has more than tg and rails combined. Django has also
increased it's pool of core devels from 2 to about 9 now, and more
are in the Q. It is not just commits that denote activity. It is the
community. Or watch the actvity on IRC - I was watching for the last
10 minutes. Nothing on rails or tg and 3 screens of talk on django.
My method of choosing an app is:
1. Check the commit activity
2. Check activity on mailing list
3. Check activity on devel mailing list
4. Check how many core devels there are
5. Check if people without commit access are having their patches
accepted
6. Check activity on IRC
Lurk and see how friendly the community is - django is incredibly
friendly. Very rare to see an rtfm.
Django leads on all these criteria. Go lurk and see.
And, for a framework, check how much you tied to the framework. You
should be able to bypass the framework without damage. Django excels
that way.
--
regards
kg
http://lawgon.livejournal.com
http://nrcfosshelpline.in/web/
Foss Conference for the common man:
http://registration.fossconf.in/web/
Other related posts: