DjangoCon 2008 Keynote: Mark Ramm
summary
Argues that Django’s codebase is effectively monolithic and tightly coupled, which leads to Django is monolithic fragmentation from the wider Python web ecosystem; cites Ginga forking the template engine and PyAMF vs DjangoAMF as duplicate efforts, notes Beaker already provides Beaker handles dog-pile signed/encrypted cookie sessions and cache regeneration, points out SQLAlchemy’s unit‑of‑work existed earlier, and reports a WSGI admin prototype (rum) works in months; recommends use WSGI middleware and to extract ORM, templating and other subsystems.
AI-written summary · about
chapters (17)
- 0:00Intro
- 1:00Why Im here
- 2:20Change the future
- 3:03Web frameworks
- 5:43Zshaped learning curve
- 11:50TurboGears vs Django
- 17:03The Django Way
- 19:17The Present
- 27:39Django is a different world
- 29:10Easy Install has some flaws
- 31:38Two ways to achieve excellence
- 33:27Django can be different
- 35:02Make Django better
- 37:05Conclusion
- 38:29Buffet
- 46:19The baggage
- 47:33Rum
related talks
29mHow Django helped us make a better conference website
26mUsing Django as a Micro-Framework: Hacking on the HTTP handlers..
31mReinventing Django for the Real-Time Web
23mStanding on the Shoulders of Giants: The Kotti Web Application Framework
22mDjango Channels Teaching a mature framework new tricks
38mdjango-cms: Friends don't let friends use Drupal.
31mHey, Python-Web-Community! What's going on?
22mBuilding Better Web APIs