Frameworkology 101 Homework
I've collected a few articles that give fairly humble assessments of the perceived trade-offs of the differing design approaches of Python's currently popular web frameworks. Refreshingly civil in their discourse, there is a lot of great insight about the approaches taken by Turbogears, Pylons, and Django. It sounds like the authors are in agreement that there remains a lot of work to do in terms of educating developers using those frameworks how to struture their applications in ways that are best suited to the framework's design.
The kickoff post was:
- Frameworks Exist for Conceptual Integrity by Adam Gomaa
With follow-ups:
- Conceptual Integrity, Django, Pylons and TurboGears by Mark Ramm
- Conceptual Integrity: Pylons and Django by Marcus Cavanaugh
- On"conceptual integrity" by James Bennett
Finally, I came across this article. Kevin Teague addresses the fact that we (we who debate these types of things) sometimes sling around a lot of OOP-ish terminology. He presents his ideas from a Zope perspective, but this article is well worth reading and he has a great sense of humor to keep in entertaining.
- The Great Python Component Swap Meet by Kevin Teague
<< Back to Unbracketed Home Post a Comment Now
Post a comment
- Markdown syntax is allowed. HTML tags will be stripped.
- CodeHilite NOT supported at this time but coming soon...
- Constructive statements and good attitudes are encouraged - being kind is better than being right
