redux VS remix

For the backend, we chose Python, Django Rest Framework. On the frontend, React, Redux, Saga, Sass. Let’s start with the backend, which was managed by Yegor. He writes about the server part of the project himself.

Use types for Redux state slices and action creators

If you are using Redux, then this is a lifesaver. We know Redux reducers can store a lot of data, and if you feed the complete store into any component, it will cause it to re-render anytime anything in that store updates.

State management is one of the useful aspects of most JavaScript frameworks, It is the management of input or data state across multiple data flows across an application. React does have in-built state management capabilities, but you’d rather use Redux or some other state management tool because it’s not the best to work with. Here is an example of state management in Redux:

Redux is a widely adopted library for managing global state in React applications. It follows a centralized store approach, where the entire application state is stored in a single JavaScript object.

redux

Alright, you knew Redux was coming.

Because the application is shared between server and browser, state is as well. If your app has a single source of state as is often the case with Redux, for example, sharing state between server and browser can be as simple as passing your state object through JSON.stringify() then adding it to a

Redux Documentation: The official Redux documentation covers everything you need to know about using Redux with React.

Next.js documentation on data fetching and state Next.js documentation on server components Redux documentation Next.js Redux Wrapper documentation

Real time data update: Remix supports Server Sent Events e.g. https://github.com/remix-run/examples/tree/main/_official-realtime-app https://github.com/remix-run/remix/discussions/2622

You don't need NextJS for SSR. There are less opinionated alternatives like Remix that was built by the React Router team and is backed by Shopify now, you can use something like Razzle or one of its alternatives for semi-opinionated pure SSR or follow the Vite Docs and just do it yourself with express.

Live reloading looks cool, I wonder if Remix is finally going to support HMR with this new release of esbuild (https://github.com/remix-run/remix/discussions/2384)

Want to deploy a site you've built using a JavaScript-based web framework? We got you - check out our tools and instructions for Gatsby and Next.JS. RemixJS is coming soon.

Note at the time of writing there is an issue with Remix github

Why acquire something that is MIT licensed?

Is this really just a talent acquisition?

https://github.com/remix-run/remix

Yes. The use of loaders and actions blurs the lines between client and server. It's really productive. There are a few gaps that need filling, one that comes to mind is internationalisation [1]

I am very surprised that NextJS has left it so long to consider mutations - they're apparently coming up with an RFC on that but it seems to be somewhat behind closed doors.

[1] https://github.com/remix-run/remix/discussions/2877

Remix (npx create-remix@latest)

For the sake of this example, I followed one of Remix’s starting tutorials and created a Docker image for it. The final code is actually available in their official repo, even with the right Dockerfile, so all the credit really goes to the Remix team 🙂. With that in my hands, the rest is a piece of cake.

But Remix only rebuilds when the apps/web folder changes, not when the package does. Enter the brand new config.watchPaths from Remix 1.6.4!