Thanks for the link to your post Reinout! So, have you made a decision about the way to go for your application?
I like the idea of using two different systems from the backend and the frontend. I am new to django (a month+), but I don't think there was ever a doubt in mind that my frontend would be .js based, and I liked that django dev let /static to be dealt with by say plain Apache, instead of enforcing python for that too. As I said, I am new to django, but I have done some experiments (wrote my own little hello world app, moved on to deploying mezzanine to dotcloud), and as I understand django is meant to be a flexible system to handle data, and was never meant to be a flexible frontend, right? Now, even though I do like the proper tools for the proper jobs, the perspective of maintaining two systems built on different technologies raises red flags. What do people think? Kind regards, Etienne On 4 May 2012, at 15:34, Reinout van Rees wrote: > I blogged about the ajax/template split regarding Django a couple of days ago > and got some helpful comments. Perhaps some of them give you some additional > feel for the matter: > > http://reinout.vanrees.org/weblog/2012/04/30/django-vs-ajax-how-far.html -- You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com. To unsubscribe from this group, send email to django-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-users?hl=en.
