mobxjs

mobx

TypeScript2015–2026

mobxjs / mobx

mobx

Simple, scalable state management.

Web Development

Explore on GitHub Read Hacker News discussions

28Distinct people

32Mentions

0Explicit recommenders

28.2KGitHub stars

REPOSITORY AT A GLANCE

What to know before exploring

What it is

Simple, scalable state management.

GitHub

Where it is used

No documented product use was verified in the last source check.

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

dustingetz/react-cursor · linked in 2 of the same discussions

Mentioned in the same Hacker News threads. That is not proof they are substitutes.

This week on Hacker News

Nov 8–Nov 15 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/15/2026, 1:03:20 AM 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 year32 dated mentions

Observed mentions: 2015-12-17 17:57:53 UTC to 2026-02-16 06:06:23 UTC.

* An incomplete calendar period is marked with an outlined bar. Its count is not directly comparable with a full period.

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges

UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
Period	Start (UTC)	End (exclusive, UTC)	Mentions	Submissions	Comments
2015	2015-01-01 00:00:00 UTC	2016-01-01 00:00:00 UTC	2	0	2
2016	2016-01-01 00:00:00 UTC	2017-01-01 00:00:00 UTC	15	2	13
2017	2017-01-01 00:00:00 UTC	2018-01-01 00:00:00 UTC	4	0	4
2018	2018-01-01 00:00:00 UTC	2019-01-01 00:00:00 UTC	4	0	4
2019	2019-01-01 00:00:00 UTC	2020-01-01 00:00:00 UTC	2	0	2
2020	2020-01-01 00:00:00 UTC	2021-01-01 00:00:00 UTC	0	0	0
2021	2021-01-01 00:00:00 UTC	2022-01-01 00:00:00 UTC	0	0	0
2022	2022-01-01 00:00:00 UTC	2023-01-01 00:00:00 UTC	4	0	4
2023	2023-01-01 00:00:00 UTC	2024-01-01 00:00:00 UTC	0	0	0
2024	2024-01-01 00:00:00 UTC	2025-01-01 00:00:00 UTC	0	0	0
2025	2025-01-01 00:00:00 UTC	2026-01-01 00:00:00 UTC	0	0	0
2026 (partial)	2026-01-01 00:00:00 UTC	2027-01-01 00:00:00 UTC	1	0	1

What Hacker News says

4 sources

dxhdr·May 6, 2017

https://github.com/mobxjs/mobx/blob/gh-pages/docs/best/react... "MobX usually reacts to exactly the things you expect it to. Which means that in 90% of your use cases mobx "just works". However, at some point you will encounter a case where it might not do what you expected. At that point it is invaluable to understand how MobX determines what to react to." I'm going to be tossing and turning tonight trying not to dream about libraries that usually work 90% of the time.

In Build Yourself a Redux

fantasyui-com·Jan 29, 2017

Heart and Love, or Ghosts in the Machine. You learn what is evolving, and you grab onto it, and evolve right with it. This is easy territory for flame wars and "whatever fits you"/"there is no best stack", but that's not the full picture. Your survival depends on what you know, life is full of surprises, death in family, cancers, car accidents, addiction, breakups, and depression. Imagine a warrior, ask him, "what is the best weapon?" and can you really imagine him saying "There is no best weapon", no, s/he would never say that. You go on the most popular code hosting website, you sort by number of stars and begin at the top. To give you a specific answer "iOS, Android and a Web App" in context of "Inventory Management - Dealer Management - Accounting - Payroll - Analytics" is Apache Cordova, (iOS, Android, and others), you use npm/node t

Read the rest

his way you will have one code base, you won't have to write the same code in multiple languages (just imagine scaling a live data sync requirement in one app and then standard REST in another -- keep it all in one language, or you will fail.) "Inventory Management - Dealer Management - Accounting - Payroll" is all pretty simple (but, please explore ideas like http://vorpal.js.org/ just to develop your API before getting to G-UI, finish your programs in the terminal first. Don't pretend programs are written GUI first, they are not. GUI is a leaky abstraction to say the least.) Don't fall for redux, relax and use https://github.com/mobxjs/mobx for actual GUI, (by the time you get to this part https://vuejs.org/ will rule) And for your Analytics front-end D3, it is a departure from standard JavaScript but it has a lot of love inside. Finally, remember develop commands/API first, get your apps working in the CLI and you will finish your program before starting it. Think about using the power of Unix (https://www.npmjs.com/package/commander), for the love of all that is mighty think about IRC, NOBODY! has time to learn to use your apps/GUI and NOBODY! ever needed to learn how to use Siri, so create a Command Line Interface version of your program and before you jump to React/Vue meditate over https://hubot.github.com/ and programs like Siri. Finally, if I was facing your requirements, I would build a wiki/forum where your users would interact with bots. Over time I'd rip put some of the robotic guts and boldly go where humanity needs to be headed, I'd replace them with what I call Artificial-Artificial Intelligence, networks of Human Mechanical Turks where anybody could participate. Neural networks are easy to train, but they are also easy to trick. Nothing will beat a random sample of Humans from across the world reaching a consensus on a tough decision. In closing, People, Real Hearts, Human Minds, powering your network would share in your profits, and you'd do your part in battling what ails us all, World's Poverty. If a mother in Rwanda and a Boy in India participating in your Mechanical Turk can find their way out of poverty, by helping your to detect fraud in your circuit. Then, you did your part, to help Humanity grow. https://www.youtube.com/watch?v=XGK84Poeynk <3

In Ask HN: What is the best tech stack to develop a SAAS Service?

true_religion·Jan 7, 2017

That really depends on your architecture. The way I have it setup, everything is in a central store, and the components only access it rather than have observables for any kind of local state. Local state is handled with boring old setState calls, so the store and data-layer is totally independent of React, and can be tested without even importing the library. > (Look for the constant MAX_REACTION_ITERATIONS) Okay... that's interesting. It dates back to Feb. 2016th[1], and I'm not caught up with that version. My pull comes from January [2]. Giving it a brief look over, it looks like they changed the codebase to allow for reacts to trigger themselves. My version doesn't allow that. It's a fatal error instantaneously. Presumably, this was done to let people write recursive functions.... but I'm not 100% sure this is a good idea. Edit: I th

Read the rest

ink my version implicitly has MAX_REACTION_ITERATIONS = 1, so observables triggering itself is an immediate error. [1] https://github.com/mobxjs/mobx/commit/a38b6a8c255d772a79dadd... [2] I know I should update, but I come from the boring Python world where you don't expect the internals of a library to change too drastically year to year.

In Lessons learned as a React contractor

unsoundInput·Jan 6, 2017

I am very confused what kind of state management MobX implements, especially after reading their current README (https://github.com/mobxjs/mobx/tree/6ed404b96a8b4074a473accd...) Is it Ember/Vue-style "mutate, observe, compute" as implied by most of their example code or Flux-style as implied by their introduction visualization (https://github.com/mobxjs/mobx/raw/6ed404b96a8b4074a473accd2...)? Do I create actions or just mutate state directly (again, visualization and some text in the readme vs examples)? How is "observer turns React (function) components into derivations of the data they render." any different from just plain React components? MobX feels like someone tried to make an easy state management solution (obviously a great goal) and in the process just threw together whatever pattern exist out there right now. It obviously works

Read the rest

for many people, considering how often someone comments about it on HN, but I wonder what makes those user stick with React vs a framework that completely embraces this approach like Vue or Ember. Is it some hard requirement on React?(EDIT: Or maybe preference of JSX?)

In Lessons learned as a React contractor