TurboGears 2.0
May 27, 2009 released a new version of the framework for developing web applications in Python.
TurboGears 2 is based on the experience and trends of modern frameworks, including TurboGears 1, Django , Rails. All these frameworks had limitations, which caused cognitive dissonance and TG2 is trying to solve these problems.That is why we have:
The above text is a compilation of the announcement from the project site.
For those not quite knowledgeable, I note that the main difference from the same Django is the use of standard and deservedly popular libraries as the main components. Which approach is better will take time, since the creators of Django, while inventing bicycles, do it very well for them.
In addition, as far as I remember, TG1 was released in the puff, so finally and not finished. Further, most of the developers' efforts were thrown on version 2, which we have the opportunity to contemplate. This fact suggests that the developers are windy and may not finish the job. Having shot at one time almost simultaneously with Django, this framework is much less common, which suggests.
In any case, the fact of the release is an occasion to see what they did there, what ideas and interesting approaches are implemented.
Project website: turbogears.org/2.0
Tutorial: www.turbogears.org/2.0/docs/main/Wiki20/wiki20.html
Changelog trac.turbogears.org/wiki/2.0/changelog
TurboGears 2 is based on the experience and trends of modern frameworks, including TurboGears 1, Django , Rails. All these frameworks had limitations, which caused cognitive dissonance and TG2 is trying to solve these problems.That is why we have:
- Multiple database support
- Horizontal data scaling
- Support for various JavaScript libraries and a new widget system that helps build complex AJAX applications with ease
- Support for multiple data exchange formats
- Expandable with standard WSGI components
The above text is a compilation of the announcement from the project site.
For those not quite knowledgeable, I note that the main difference from the same Django is the use of standard and deservedly popular libraries as the main components. Which approach is better will take time, since the creators of Django, while inventing bicycles, do it very well for them.
In addition, as far as I remember, TG1 was released in the puff, so finally and not finished. Further, most of the developers' efforts were thrown on version 2, which we have the opportunity to contemplate. This fact suggests that the developers are windy and may not finish the job. Having shot at one time almost simultaneously with Django, this framework is much less common, which suggests.
In any case, the fact of the release is an occasion to see what they did there, what ideas and interesting approaches are implemented.
Project website: turbogears.org/2.0
Tutorial: www.turbogears.org/2.0/docs/main/Wiki20/wiki20.html
Changelog trac.turbogears.org/wiki/2.0/changelog