Why I’m throwing out React and going back to Angular 1.x

Re:Why I’m throwing out React and going back to Angular 1.x by jaypaulynice on Tuesday March 14, 2017 @06:40PM (#13872150)

I've used Backbone/Marionette, Angular, and React at this point. I think Backbone/Marionette is the best framework so far maybe because it was the first one I did a big project on. Backboe/Marionette has very clear separation of concerns...the only true MVC framework among the 3. React is great for reusable components, but the tooling around it is so backward...I feel like I'm writing a java application and I need to piece things together.

Btw I'm working on a django/react application and I have yet to figure out how to not duplicate the react routes in django. It defeats the purpose of a single page app because I don't want to reload all the same resources because a small piece of the app changes...how do you fix this?

[ Parent | on HN ]

Re:Why I’m throwing out React and going back to Angular 1.x by ptmcc on Tuesday March 14, 2017 @06:46PM (#13872201)

I agree and think Backbone/Marionette is under appreciated.

[ Parent | on HN ]

Re:Why I’m throwing out React and going back to Angular 1.x by tracker1 on Tuesday March 14, 2017 @07:32PM (#13872523)

Make your 404 handler return your baseline react without preloaded state. If you use node server-side it becomes easier to do universal rendering and state injection.

[ Parent | on HN ]

Re:Why I’m throwing out React and going back to Angular 1.x by jaypaulynice on Wednesday March 15, 2017 @12:36AM (#13873848)

Thanks! I don't want to hit the web app at all...I want to load all my static files once and then it's all client side...getting data from the rest service when it needs it...

[ Parent | on HN ]

Re:Why I’m throwing out React and going back to Angular 1.x by tracker1 on Friday March 17, 2017 @01:04PM (#13895697)

You can do that... if you want to handle all the routes, just make your 404 handler on the server return your base html then.

[ Parent | on HN ]