cerebral VS react-redux

Today's mainly going to be focused on the frontend, because I want to introduce this state management system that I've been really digging lately. It's called Overmind, the same team that made Cerebral. Overmind is somewhat similar to Cerebral, but it supports TypeScript and it's... well, it's not abandoned.

Now we need 2 libraries for redux, the first one has the redux API and the second one has the Redux configured to be used with React.

> > I maintain my 2017 apps including major version bumps with no issues today

> Sorry but I have to call bullshit on that, unless you’re taking about tiny one page “apps”

What a strange stance. It's a React/MobX collaborative model editing internal tool deployed in production to users who generate and analyze models with it. It started on Webpack 2 and React 15 and MobX 4, now it's on Webpack 5 and React 17 and MobX 6. I of course had to update some babel configurations but it was much more version bumping than configuration rebuilding. It still uses decorators and looks like complete dog-shit, and that's my point: the same tricks and patterns available then are not only there, but working identically now.

Re: native, I don't believe in React Native or any webview-based "native" replacement anyways, but it's easy to do this as my user-base is interacting with this app from their company-provided laptops anyways. I would willingly concede React Native is an environment with churn, I don't really recall RN every reaching meaningful stability

> Redux is dead in the water

https://www.npmjs.com/package/redux shows 7M downloads weekly

https://www.npmjs.com/package/react-redux shows 5M

https://www.npmjs.com/package/@reduxjs/toolkit shows 1.5M

MobX / MobX React are around 1M/700k

Your list of "flummox / redux / unstated / mobx / mobx-state-tree / xstate / apollo / apollo-link-state / swr / react-query / zustand / recoil / jotai" seems to peak at 500k with the exception of "react-query", which I don't really see as applicable to a conversation about state management, and perfectly illustrates my point that there's new stuff but you don't need to know it

> you say it’s #1, but Redux is dead in the water

I never personally believed in Redux, it struck me as a terrible pattern from the start, thus why I selected MobX; but I find it difficult to believe that you really think React Context scales the same way building an external state management tree does. I like React Context, but it doesn't do a very good job of hiding away complexity from the developer as the application grows. Not to mention it does no render-optimization for you.

Again, I'm not saying things don't change or that there's not alternatives, but I am saying that someone who learned fundamentals in 2017 is still able to get up-to-speed in the updated versions of the library kings of 2017 in virtually no time, and deliver standard-fare webapps. I say this because I've worked at the same place for over 5 years, I use the same tools, and my users regularly are telling me the tools my team puts in front of them are the gold standard. The churn is long gone, everything you describe would have perfect analogues in any other popular modern language / library ecosystem.

If you are familiar to web developing or programming in general, you have heard the term, React.js, being thrown around. React is a library that makes declarative UI easier to accomplish using hooks and components. Essentially, you can write a chunk of code (mainly using jsx which is like html's sibling but cooler) into a one-liner(). It is declarative because the outcome of said component is predictable and easier to debug than imperative code. You also have these things called hooks that are built-in functions that make handling state, behavior and other logic easier to do in React in comparison to vanilla JavaScript. Also, you can write it anywhere in your project, (hence why React is a library and not a framework although people call it framework because it competes above and beyond compared to Angular and Vue) so you have more flexibility. It also has this thing called Redux which is a library that handles complex state management but we won't get into that 🤒 because there are better and easier ways to manage state in React like using the Context api. I will go more into when to start learning React in a future post soon.

my guess is the react-redux is written in typescript, in the implementation the function is typed in the

UPDATE 2Watching the breaking changes of react-redux, I was able to understood that the problem was how I pass the store (breaking changes).

For example, upgrade React Redux to v8 or SWR to 1.1.0