I'm not in a position to draw a comparison between the Grails and Django, but I would say that Django's package ecosystem, and in particular for your use case it's API frameworks, are really rather great.
Again, I've no idea how Grails compares, but Django TastyPie<http://tastypieapi.org/> and Django REST framework <http://django-rest-framework.org/> are both excellent and could save you stacks of time. Regards, Tom On Sunday, 13 January 2013 19:37:20 UTC, tapan pandita wrote: > > 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/-/J910gUiisNIJ. 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.
