Hi I have tried both and decided to stay with Django. Both frameworks are great, but it was annoying that Grails did some compilation every time I changed something. Sometimes it was fast, sometimes it was long enough to start to read blog articles and be distracted from main work. There was even worse situation when I wanted o use debugger - every time i started debugging session whole Grails needed to be started (compiling, configuring spring security, etc).
Regards W dniu niedziela, 13 stycznia 2013 20:37:20 UTC+1 użytkownik tapan pandita napisał: > > Hey Guys, > > We have an initial version of our product ready on Grails. However, before > we move forward, we want to make a call between using Django or Grails. The > product is basically an API and some templating. The team comprises of > people who are comfortable with both frameworks and can easily make the > switch from one to the other. Based on the research I've done online, I > feel both frameworks are essentially the same. Groovy is just about as easy > to develop in as python and ecosystem-wise Java doesn't have any advantage > over Python (at least as far as the web is concerned). Also, Grails can do > pretty much everything that Django can do (including schema migrations now > which people seem to complain about earlier). Personally, I am a django guy > and haven't developed a lot in Grails (just basic stuff). What would be > some compelling arguments to switch to Django over grails or should we > stick with grails? -- You received this message because you are subscribed to the Google Groups "Django users" group. To view this discussion on the web visit https://groups.google.com/d/msg/django-users/-/R5LeiQvszvEJ. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/django-users?hl=en.
