Simplifying Web Framework Deployment on Shared Hosting
On Dreamhost freaking out because they can’t get Rails deployed reliably.
Django’s cache framework
All frameworks should approach caching the way Django does. The core app/origin framework does no real caching but provides utility/helper methods for setting standard RFC 2616 cache related headers on the response easily and correctly. A completely separate set of caching goo (“middleware”) sits between your app and performs the actual caching based purely on the headers set by the origin. The benefit to this approach is that caching is totally independent from the app framework and can be swapped out for a true gateway (“reverse proxy”) cache at any time.
Google App Engine
Christmas in Python land! Run Python/WSGI code on Google’s infrastructure. This is an incredibly H U G E win for the Python web community and further validates WSGI’s architectural awesomeness.
I Can Haz Hardcore Forking Action
More praise for GitHub from a small team of Django hackers that built a site in three hours on one night with a little help from git…
Django People
Simon Willison’s latest project makes it easy for people developing in Django to hook up and get laid (since they have so much free-time due to developing in Django).
What PHP Deployment Gets Right
Ian takes a look at some of the attributes of PHP’s deployment model, why they work so well (for PHP), and why other environments have such a hard time duplicating them.
10 Reasons Why Django kicks Ruby on Rails’ collective ass.
Wherein the author lists 8 reasons (maybe 3 of which are approaching objective or even valid) and also spells Adrian’s name wrong: “Adrian Zolovaty”. Ruby/Python flame-bait is exactly what we need.
A fundamental way newspaper sites need to change
Outstanding piece. Adrian ought to write more often. Microformats.org could really use someone with Adrian’s background to squash some of the “why?” type questions.