Re:Why we needed Redux in the past, and don’t any more
by js_question on Friday September 07, 2018 @04:29AM
(#17932719)
I am an EE doing some web development on the side. Since a few weeks ago, my stack was mostly Flask (backend) + JQuery (frontend). My web apps were always light on the front end. Then I wanted to experiment with React. So far, I really like the declarative component design but don't like the Single Page App approach. Is there a way to render components on the server for each page individually without having to set up a new react project/web pack build step for each page?
[ Parent
| on HN ]
Re:Why we needed Redux in the past, and don’t any more
by andrewmu on Friday September 07, 2018 @04:55AM
(#17932804)
Next.js (https://nextjs.org/) lets you render pages on the server but have your React app behave normally after that. It's potentially useful for SEO and reducing latency for final page display.
Re:Why we needed Redux in the past, and don’t any more
by testb on Friday September 07, 2018 @04:36AM
(#17932740)
The search term you want is 'react ssr' or 'react server side rendering'
Re:Why we needed Redux in the past, and don’t any more
by js_question on Friday September 07, 2018 @05:11AM
(#17932866)
Followup question. Does it actually make sense to use React and render it server side only to get declarative component design?
I can totally see the use case for React for web apps which provide a lot of user interaction on the frontend. But for all other web apps it doesn't seem to make sense as you also have to handle quite a few disadvantages (e.g. SEO unfriendly, user can't copy URL and send to a friend)
Am I missing something?
Re:Why we needed Redux in the past, and don’t any more
by testb on Friday September 07, 2018 @03:09PM
(#17936864)
There's a good chance you're not missing something - Lots of people don't like SPA's because the consistency of a normal website isn't there. The best SPA's I've used don't actually feel like SPA's and it's worth mentioning that no one seems to mind Amazon/Github/Youtube not using React/Vue/Angular
Re:Why we needed Redux in the past, and don’t any more
by ohhellno on Friday September 07, 2018 @07:13AM
(#17933373)
Next will manage your URLs and all the SSR does is generate static files for each page with the base data and loader so future requests grab static JSON versions of the pages. There is no need for it to be rendered in the server. You could do it locally and push the resulting files up. URLs will work as you expect them to.
Re:Why we needed Redux in the past, and don’t any more
by dynamite-ready on Friday September 07, 2018 @04:53AM
(#17932791)
Gatsby JS is worth a look. It's basically a framework to create static pages server side, with React's constructs and tools.
You can even use data from your Flask based backend directly, to create the static pages.