The admin not allowing email addresses as usernames still irks me, such a seemingly pointless restriction in this day and age.<p>Decent response to the original article, though I have to admit that I have a pet peeve about developers declaring libraries/frameworks "insufficient", "lacking" or "fundamentally flawed" as an excuse to write things themselves. Or maybe I'm just grumpy.
'There are a few other questions raised, some of which I agree with(”Sadly, it[the admin app] struggles a little bit with nullable fields and is tricky to customize.”), and some which I dont, (”I will never write CSS by hand again.” - You shouldn’t be, someone else on your team should be doing that.)'<p>Ugh, this is just a totally unrealistic and out-of-touch argument. Look, I work on a website, and it's me and one other guy, and we both have to write frontend and backend code. It's not even remotely reasonable for us to just stop writing frontend stuff and tell our boss to hire someone else to do it. I fully understand why the Django templating language is the way it is, and it even makes sense, but it's not perfect for all situations, one of which is when the user is a big boy and can handle the responsibility of using full-blown python in a template.
(I wrote the original Dropping Django post)<p>I wrote a quick comment at <a href="http://uswaretech.com/blog/2009/08/a-response-to-dropping-django/#comment-2093" rel="nofollow">http://uswaretech.com/blog/2009/08/a-response-to-dropping-dj...</a><p>Maybe I wasn't clear enough, or maybe this is just guaranteed flame war territory. But I think this comment sums up what I was trying to say better than anything: <a href="http://news.ycombinator.com/item?id=773510" rel="nofollow">http://news.ycombinator.com/item?id=773510</a><p>I'm going to try to write more about our URL routing and authorization soon.