Why TurboGears?

[Lee Olayvar]

I'm just curious, as these python web frameworks are new to me (stuck with PHP in the past.. and hated every minute of it.), but everything keeps giving my Django is coming out on top. Is TurboGears soon to make a lot of ground, or has already, etc?

Just wondering, so i know for my own future tortuga-independant projects.

Thanks,
--
Lee Olayvar

[Sami Dalouche]

There is a huge difference of philosophy between Django vs TurboGears.

Django embraces the 'no-external-dependency' approach, so its
developers are basically re-creating every piece of the infrastructure
in order to create a cohesive set of components. To some extent, it
shares the same philosophy as Zope.

TurboGears embraces the 'best-of-the-breed' approach, where they try
to pick whatever they consider the best components and integrate them
together. To some extent, it shares the same philosophy as Pylons, so
Pylons and TG developpers are working hard in order to share
components.

So the choice between both frameworks mainly depends on whether you
like reinventing the wheel in order to have 100% integrated
components, or whether you accept some temporary impedance mismatch in
some places.

regards,
Sami Dalouche

[Florent Aide]

Certainly because TG is geared toward reusing already existing
components. In TG you'll be able to choose your templating engine,
your orm and in TG2 any WSGI component you want.

In Django you'll have to use their orm, their templating
engine...(partially false I know but yet... the primary focus is not
on reusing outside components)

This is just an outsider (tortuga-wise) POV and is obviously biased
toward TG since I am a core TG developer :)

If you just think in terms of volume (as opposed to quantity) you'll
be moving to Php or Java instead of Python. If you think in different
terms (the complete definition of those would be lengthy and subject
to speculation) you'll choose Python. (grin)

Florent.

[Mark Ramm]

There are several features of TurboGears 2 out of the box that are not
availble in django:

* Ability to get and save complex graph of objects via the ORM
* Ability to use multiple database connections, and easy support for
two phase commit
* Ability to easily add WSGI middleware exactly where you want in the
execution stack
* Ease of support for multiple views of the same data to support html,
json, rss, etc all from the same controller method
* Out of the box support for a stand-alone python server that can be
used in production
* Ability to easily dispatch to and from other WSGI applications

It's this last one which is critical for Tortuga, because it makes it
possible to mount a tortuga site into a TG2 app, or vice versa, and I
think this kind of interoperability is critical if we're going to be
building up sites from smaller components.

--Mark Ramm

On Fri, Nov 21, 2008 at 9:14 AM, Lee Olayvar <leeol...@gmail.com> wrote:

--
Mark Ramm-Christensen
email: mark at compoundthinking dot com
blog: www.compoundthinking.com/blog

[Lee Olayvar]

Very good descriptions, thank you :)