Angular is really wonderful, and I use it with several Django projects. But the two are agnostic about each other. All Angular needs from the back-end is a solid JSON API to work with and a few core back-end features like handling authentication. Modern JS frameworks like Angular, sadly, make the back-end almost (but not quite) irrelevant. The reason I use Django as the back-end is because Django REST Framework is so freaking fantastic as an API generator. I'm really hoping that once Django 1.7 lands and migrations are in, the dev team will turn its attention to native RESTfulness.
You do lose a lot of Django goodness when adopting a client-side framework though. For example, you can't traverse model relationships however and whenever you want - any data you need in the view needs to be added to the API first. This isn't *quite* ready for public consumption yet, but here's something I've been working on - a kit for building hybrid Django + Angular sites: https://github.com/shacker/tristano On Saturday, June 21, 2014 4:03:17 PM UTC-7, zweb wrote: > > > I was looking at Angular and looks like it does many of the thing Django > Templates does but on the client side. > > Are you using Angular with Django? How is the experience? What are the > /pros/cons? What are using django for and what are you using angular for? > Is django pretty much a rest framework with business logic and DB access? > (when used with Angular) > > -- You received this message because you are subscribed to the Google Groups "Django users" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-users+unsubscr...@googlegroups.com. To post to this group, send email to django-users@googlegroups.com. Visit this group at http://groups.google.com/group/django-users. To view this discussion on the web visit https://groups.google.com/d/msgid/django-users/a1c94581-afe2-4a39-844e-72abc7973fa2%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
