A constructive writeup of why you’d want something other than the default Django ORM, and how to use SQLAlchemy instead. Amazingly for this debate, it appears to be free of any unnecessary name-calling.
But the slashing anecdote is from March 2006, which you recall is a period of greater girl-on-girl assaults than 2007, which makes it a horrible data point from which to project an increasing trend of vicious assaults.
I’m still extremely skeptical of the notion of a “portable” social network, but it’s nice to see people working on it.
Support for SQLAlchemy and Django is planned. Assuming the various folks working on MS-SQL support wrap up soon, this would give Django a pretty nice foothold in terms of supporting popular “enterprise” database solutions.
Why is it that the 19th century African villager will pick the right solution (you picked #2, right?) and the 21st century software developer will often go for something akin to solution #1?
Worth reading all the way through.