Can’t agree more with this…I have felt this time and again…..the odd thing is, I decide not to dig usually when there’s deadline nearby or a clear goal ahead. In other cases am quite happy digging and morning around.. I enjoy doing that monkeying :-)
But with django, every time i decide, i do not want to look into this source for now, i seem to miss a deadline and end up coming back to look at the source. partly because am pushing into areas rather new in django and partly because, i don’t read the documentation thoroughly, but just enough to get what i need to get done.
I think django is overrated for developers… the templating system is inconsistent…
And worse, doesn’t give a clue as to figure out the problem.. there are sometimes when you change the form and the template system still just ignores the new fields.. no idea why/what to do.. even a restart of the dev server doesn’t work…..guess googling and filtering through a lot of the drivel will get an answer.. but it really is an annoying amount of work for something that seems so intuitive..
And more mess from django, this time inspired by Relational SQL see here . The reason/explanation given for won’t fix is very casual and assumes a highly normalized database design. Turns out, real life ain’t that perfect with tables and relations so very clearly defined.
I don’t know what am supposed to damn for this, the dogmatic relational model whose chosen tradeoffs doesn’t make much sense in today’s cheaply available storage media or the set of compulsive habits, picked up by programmers(including me) following and depending on the relational model. And as the outrage subsides, quiet despair settles in sneakily…