|
|
|
|
|
|
by mmorris
6131 days ago
|
|
|
I'm not so sure the problem comes down to a fear of admitting getting it wrong in the first place, as much as it is a desire to hold tightly to a rule for template design that the creators feel has served Django well (keeping the templates simple). When it comes to your own rules, everyone is a little afraid of the dreaded 'slippery slope', no? For the record, I agree that something this basic should be built in to Django. I certainly use it often, I'd be a bit surprised if its use wasn't common in the Django community. |
|
|
That's the whole point here, isn't it?
They're keeping the language simple at the expense of making the templates more difficult to read and less efficient.
There is no slipperly slope here, only in the eyes of those who want to present it that way. It's a simple design flaw that has been kept in its place against a fair bit of community pressure.
There are other issues like this, for instance at the ORM level, have a look here for a fine example of that, you won't even have to leave this site:
http://news.ycombinator.com/item?id=523661
If it is broken, and people put up very solid arguments for it being broken the idea is to fix it, not to come up with all kinds of arguments 'why it isn't broken'.
What is broken or not depends on your use case. If you ORM or template language forces people to twist themselves in to all kinds of weird shapes to jump through your hoop you should make life easier for them, even if your personal experience is different. It's a matter of viewpoint, and by playing 'dictator' you are making life harder for others.