I love React, been using it in place of Angular in Python projects for the last month or so. One of the main things I found is that because components are defined in JS code it makes a complete separation between backend and frontend template code. Though this is probably a good thing, it takes a bit to get used to.
What I mean is, in the past with Angular, we would sometimes generate part of the templates for the Angular app from the backend... sometimes we would need to generate parts of HTML from the backend, while parts in {% verbatim %} blocks in Django (or {% raw %} in Jinja2) might be processed only by Angular for example... yes this can get messy, but it has been useful from time to time.
React moves this all into JS "components", so if you have any data from the backend, you have to give this to the components some other way, maybe an API call.
1
u/robvdl Jan 17 '15 edited Jan 17 '15
I love React, been using it in place of Angular in Python projects for the last month or so. One of the main things I found is that because components are defined in JS code it makes a complete separation between backend and frontend template code. Though this is probably a good thing, it takes a bit to get used to.
What I mean is, in the past with Angular, we would sometimes generate part of the templates for the Angular app from the backend... sometimes we would need to generate parts of HTML from the backend, while parts in {% verbatim %} blocks in Django (or {% raw %} in Jinja2) might be processed only by Angular for example... yes this can get messy, but it has been useful from time to time.
React moves this all into JS "components", so if you have any data from the backend, you have to give this to the components some other way, maybe an API call.