VAvaland·Jul 29, 2020
Unstated (https://github.com/jamiebuilds/unstated)
In Redux Overview and Concepts – Reimagined Redux Tutorialjamiebuilds
unstated
JavaScript2018–2020
jamiebuilds / unstated
unstated
State so simple, it goes without saying
9Distinct people
11Mentions
0Explicit recommenders
7.7KGitHub stars
What to know before exploring
What it is
State so simple, it goes without saying
GitHub
Where it is used
No documented product use has been verified yet.
What people are saying
No recommendation phrase was found in the indexed comments.
No classified warning is attached to this page. Read the discussions before treating silence as approval.
Also in these discussions
No other repository is repeatedly linked in the same discussions.
This week on Hacker News
Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 5:04:57 PM UTC.
No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.
Mentions over time
HN mentions by month11 dated mentions
Observed mentions: 2018-04-10 20:57:40 UTC to 2020-07-29 12:28:10 UTC.
Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.
View mention counts and date ranges
| Period | Start (UTC) | End (exclusive, UTC) | Mentions | Submissions | Comments |
|---|---|---|---|---|---|
| Apr 2018 | 2018-04-01 00:00:00 UTC | 2018-05-01 00:00:00 UTC | 2 | 1 | 1 |
| May 2018 | 2018-05-01 00:00:00 UTC | 2018-06-01 00:00:00 UTC | 0 | 0 | 0 |
| Jun 2018 | 2018-06-01 00:00:00 UTC | 2018-07-01 00:00:00 UTC | 0 | 0 | 0 |
| Jul 2018 | 2018-07-01 00:00:00 UTC | 2018-08-01 00:00:00 UTC | 0 | 0 | 0 |
| Aug 2018 | 2018-08-01 00:00:00 UTC | 2018-09-01 00:00:00 UTC | 1 | 0 | 1 |
| Sep 2018 | 2018-09-01 00:00:00 UTC | 2018-10-01 00:00:00 UTC | 0 | 0 | 0 |
| Oct 2018 | 2018-10-01 00:00:00 UTC | 2018-11-01 00:00:00 UTC | 0 | 0 | 0 |
| Nov 2018 | 2018-11-01 00:00:00 UTC | 2018-12-01 00:00:00 UTC | 0 | 0 | 0 |
| Dec 2018 | 2018-12-01 00:00:00 UTC | 2019-01-01 00:00:00 UTC | 0 | 0 | 0 |
| Jan 2019 | 2019-01-01 00:00:00 UTC | 2019-02-01 00:00:00 UTC | 1 | 0 | 1 |
| Feb 2019 | 2019-02-01 00:00:00 UTC | 2019-03-01 00:00:00 UTC | 2 | 0 | 2 |
| Mar 2019 | 2019-03-01 00:00:00 UTC | 2019-04-01 00:00:00 UTC | 0 | 0 | 0 |
| Apr 2019 | 2019-04-01 00:00:00 UTC | 2019-05-01 00:00:00 UTC | 1 | 0 | 1 |
| May 2019 | 2019-05-01 00:00:00 UTC | 2019-06-01 00:00:00 UTC | 0 | 0 | 0 |
| Jun 2019 | 2019-06-01 00:00:00 UTC | 2019-07-01 00:00:00 UTC | 0 | 0 | 0 |
| Jul 2019 | 2019-07-01 00:00:00 UTC | 2019-08-01 00:00:00 UTC | 0 | 0 | 0 |
| Aug 2019 | 2019-08-01 00:00:00 UTC | 2019-09-01 00:00:00 UTC | 0 | 0 | 0 |
| Sep 2019 | 2019-09-01 00:00:00 UTC | 2019-10-01 00:00:00 UTC | 0 | 0 | 0 |
| Oct 2019 | 2019-10-01 00:00:00 UTC | 2019-11-01 00:00:00 UTC | 1 | 0 | 1 |
| Nov 2019 | 2019-11-01 00:00:00 UTC | 2019-12-01 00:00:00 UTC | 0 | 0 | 0 |
| Dec 2019 | 2019-12-01 00:00:00 UTC | 2020-01-01 00:00:00 UTC | 0 | 0 | 0 |
| Jan 2020 | 2020-01-01 00:00:00 UTC | 2020-02-01 00:00:00 UTC | 0 | 0 | 0 |
| Feb 2020 | 2020-02-01 00:00:00 UTC | 2020-03-01 00:00:00 UTC | 0 | 0 | 0 |
| Mar 2020 | 2020-03-01 00:00:00 UTC | 2020-04-01 00:00:00 UTC | 0 | 0 | 0 |
| Apr 2020 | 2020-04-01 00:00:00 UTC | 2020-05-01 00:00:00 UTC | 2 | 0 | 2 |
| May 2020 | 2020-05-01 00:00:00 UTC | 2020-06-01 00:00:00 UTC | 0 | 0 | 0 |
| Jun 2020 | 2020-06-01 00:00:00 UTC | 2020-07-01 00:00:00 UTC | 0 | 0 | 0 |
| Jul 2020 | 2020-07-01 00:00:00 UTC | 2020-08-01 00:00:00 UTC | 1 | 0 | 1 |
What Hacker News says
11 sourcesReact team made the wrong separation of problems with hooks.
Class component should lose its ability to render and replace it with attach functional renderer. In its place, class component should have composable and detachable state and substates with their own lifecycle, each communicating via events within the same context.
It will be truer to `ui = fn(state)` principle.
This is a result of contemplation after learning what the functional people and rust community are doing, and then coming back in front of my laptop showing my professional project in React and TypeScript.
Unstated (https://github.com/jamiebuilds/unstated) is a library that helps scoping and lifecycle separation.
I used in-house event library but there are a couple of libs out there providing this functionality like https://github.com/KeesCBakker/Strongly-Typed-Events-f
Read the rest
or-Typ...
It took me months to experiment and reach the decision which finally helps the team to write and iterate faster. I hope this will help everyone facing those React problems.
There are some which require less boilerplate and actually are (partially significantly) smaller in size.
https://github.com/jamiebuilds/unstated
https://github.com/dai-shi/react-tracked
https://github.com/react-spring/zustand
https://github.com/diegohaz/constate
(there are more, but these may be among the most popular)
You can find a comparison (and more) here: https://github.com/dai-shi/lets-compare-global-state-with-re...
In Redux – Not Dead Yet (2018)Being OOT and throwing in unpopular opinion:
Redux fails in recreating the success of elm architecture. Without the static typing of elm, it ends up being painful to use.
Redux drives inexperienced developers to put everything into the store, making it a god-object. See: https://news.ycombinator.com/item?id=14669980
Redux middlewares allow changing return type, which makes it hard to implement static typing to it.
Redux without middlewares needs additional code to work with static typing. See: https://github.com/piotrwitek/typesafe-actions
Redux expose actions and reducers to developer, which is a state management mechanism that usually are written the same over and over again.
I sound harsh on it, but I want devs around the world to not go through the pain of using Redux on large scale project involving a lot of people.
Redux is good for
Read the rest
education. It introduce the concept of immutability, higher order function. I learn a lot from it. Nevertheless, it is a pain to use on big projects.
React's setState is friendlier to devs. Unstated https://github.com/jamiebuilds/unstated (but not unstated-next), is a detached version of React's setState with additional `.subscribe` method and Promise as return. It is very good in both developing and communicating business flow. UnstatedContainer method can be treated as counterpart of Redux's action.
What is missing now from the client-side web development is an in-app event library. Usually people would put domain-objects to Redux to solve the inter-component communication. This is, against the functional programming (which promotes immutability, higher order functions), introducing the possibility side-effect.
In-app event library should replace this behavior so that messages can be passed through events from one component to another that resides on different component-tree, which may want to act differently. This is some sort of implementing mini kafka/rabbit-mq-like behavior inside the your web app with minimum resource required.
Author here. I've kind of rewritten unstated [0], because building large-ish apps with it was starting to become troublesome. Overstated is:
- Even simpler: connecting to the stores via `useStore` of `connect` is much more ergonomic than unstated's `Subscribe` component.
- Much more performant: it encourages the user to use only the state/methods he needs (via a selector function) so it can re-render components only when absolutely necessary.
- TypeScript friendly: our `useStore` hook is fully typed and makes writing components a joy (I think this is huge once you actually get to try it).
What do you think? :)
[0] https://github.com/jamiebuilds/unstated
In Show HN: Overstated – React state management library that's delightful to useThe concept of having one store with associated actions is a great one, but Redux itself has an enormous amount of boilerplate having to do with the fact that you do all calls into your state functions as events which is completely unnecessary. Every project I’ve worked on using redux ends up having a ton of different abstractions just to reduce the redux event boilerplate overhead. I use unstated https://github.com/jamiebuilds/unstated , which gives you the beneficial central store structure without the silly event concept.
In Ask HN: How do you manage state in your React application?Seems to solve a similar issue as https://github.com/jamiebuilds/unstated
In Show HN: Simple way to share state using React Hooks and ContextWow, relax man! You don't have to defend redux with your life!
I have to work on a daily base with redux because almost every stupid company is using that nowadays. Some codebases are so horrific that I simply quit the job and find something better.
I actually said why it is poor in design: endless switch statements with reducers, do you think that is great design? Every component that wants to use a store needs to 'connect' to it with a higher order component, ever seen chains of hoc's and still know what's going on? Then you need to write time and time again mapStateToProps and mapDispatchToProps. Do you think that's great design? Even if there would be no other state management system yet, it still sucks. Even Dan Abramov says you probably don't need redux, still everyone is using it for the most simple apps.
You might want to use a ro
Read the rest
uter, well you're kinda locked into redux so you need redux-router. Example from the redux-router repo:
import React from 'react';
import { combineReducers, applyMiddleware, compose, createStore } from 'redux';
import { reduxReactRouter, routerStateReducer, ReduxRouter } from 'redux-router';
import { createHistory } from 'history';
import { Route } from 'react-router';
This, for just wanting to use a fucking router that works along with my store! You think that is great design? React is great design IMHO, not redux. Dan Abramov is a great guy, highly talented, times more intelligent than I am, but his design principles are really poor. Same counts for hooks, a fun experiment for a counter demo, but poor design for larger apps. I hope it will never become a hype too.
Redux is just one of the many flux implementations. Not the best, but a flavour that you may like or dislike. Unstated is a client store that is a wrapper around the new React Context API: unstated: https://github.com/jamiebuilds/unstated
Context is great to work with and solves most of our usecases. I also recommend looking into Unstated[0], simple api and easy to implement.
[0]https://github.com/jamiebuilds/unstated
In Redux vs. The React Context APIUnstated – A simple state management library for React
3 points · Open discussionThere are tons of options for State Management before you even need Redux.
Check out:
Context API: https://reactjs.org/docs/context.html
Unstated: https://github.com/jamiebuilds/unstated
MobX: https://github.com/mobxjs/mobx
In Learn React by building a web app