Django Pain Points

15 May

1) Template system :- you have to learn the a whole new config language

2) Too much special purpose abstraction , eg for SQL etc ..

Note that I am still learning πŸ˜› . Good thing though is that once everything is setup , it is very easy to make changes . But getting it setup initially is a pain . Yeah I nearly completed the build automation stuff in python, using django for web ui !


5 Responses to “Django Pain Points”

  1. Mickey September 8, 2011 at 9:03 pm #

    You’ve got it in one. Couldn’t have put it btteer.

  2. Suresh Balasubramanian March 6, 2012 at 8:25 pm #

    I don’t understand what you mean by “Too much special purpose abstraction , eg for SQL etc”. Are you referring to Django models? If yes, I think you should look at it more closely. Django models is a cool OR layer.

  3. sandeepmathew March 6, 2012 at 10:06 pm #

    Django models covert into SQL statements ultimately right , i did not like the idea of learning a new “Django” way of doing SQL . I prefer something more lightweight and naked like for eg

  4. Suresh Balasubramanian March 7, 2012 at 12:20 pm #

    I understand where you are coming from. Whether to use Django models or not is completely upto you. You can even you SqlAlchemy as your OR layer or create your own OR. If you are building large apps with lot of DB requirements you will always be benefited by using an OR layer. That is what Django wants to tell the developers by including their own OR. Contrary to the belief Django models is not something you have to eat compulsorily.

    I agree to your point that Django is a bit bloated when compared to micro frameworks like bottle or web2py. At the same time you have lots of reusable apps/plugins, documentation/tutorials/blogs available for Django, hence people will be tempted to go the Django way.

    • sandeepmathew March 7, 2012 at 11:15 pm #

      πŸ™‚ . Well … I am not an expert at Django and have not used it for a considerable length of time , Most of it are my initial impressions πŸ™‚ . Off topic .. but python has lot of potential for test Automation πŸ™‚ . I consider it better than C# for test automation purposes !

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

%d bloggers like this: