you are right. i am arguing based on the assumption that this: being comfortable in Django and wanting to keep that is a bad idea. because whoever is doing th

you are right. i am arguing based on the assumption that this: being comfortable in Django and wanting to keep that is a bad idea. because whoever is doing that is missing out on a lot of potential. sure, there are many cases where sticking with django for everything is the right choice, but that's not always true, and i am trying to argue that there is a benefit to exploring the alternative. i was a backend developer too, django, laravel, others,, and i shunned javascript as much as i could, but when i discovered angularjs (the first version, before it was popular) it just won me over as the better way to build frontends. in particular, not having to track state in the server, i feel, makes the whole development process so much easier. i could summarize it thusly: i would use a lightweight option only if the site is mostly stateless (which many content sites tend to be) but as soon as it is necessary to track state, i find a frontend framework talking to an API is the better choice, because tracking state in the browser is so much easier.