The admin not allowing email addresses as usernames still irks me, such a seemingly pointless restriction in this day and age.
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.)'
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.
If you want to use full blown python in a template - use a template tag.
What scenario do you require python in a template? I am a big boy, and the few times I have thought about needing python in a template I realized I need to do a bit more work in the view.
I think it is a great example of protecting 'big boys' from themselves. A year from now when you don't remember how you designed a section of your code you can trivially debug and test instead of trying to sort through logic in the presentation layer.
Also, it makes unit testing much easier having logic stop at the views.
The implication that designers are not "big boys" is offensive. I will parry with: "big boys" often wield power they don't understand to theirs and everyone else's detriment. More importantly, if all the big boys get hit by a machismo bus who will be around to cook the spaghetti?
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: http://news.ycombinator.com/item?id=773510
I'm going to try to write more about our URL routing and authorization soon.
I'm not a python or django developer, so I can't comment on the technical merits of what either of you are saying. However, this exchange has left me with a lot of respect for both of you. It's been very polite and professional, and hasn't fallen into the usual vitriol and holy wars.
[+] [-] tvon|16 years ago|reply
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.
[+] [-] Davertron|16 years ago|reply
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.
[+] [-] mrtron|16 years ago|reply
What scenario do you require python in a template? I am a big boy, and the few times I have thought about needing python in a template I realized I need to do a bit more work in the view.
I think it is a great example of protecting 'big boys' from themselves. A year from now when you don't remember how you designed a section of your code you can trivially debug and test instead of trying to sort through logic in the presentation layer.
Also, it makes unit testing much easier having logic stop at the views.
[+] [-] jjames|16 years ago|reply
[+] [-] snprbob86|16 years ago|reply
I wrote a quick comment at http://uswaretech.com/blog/2009/08/a-response-to-dropping-dj...
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: http://news.ycombinator.com/item?id=773510
I'm going to try to write more about our URL routing and authorization soon.
[+] [-] IsaacSchlueter|16 years ago|reply