I used React for years, and the most productive, fun stack I ever worked in was MobX. It& #39;s basically the cheat code for React

It& #39;s heart-breaking to see Concurrent Mode basically break MobX, with the response being "well they& #39;re breaking the rules so https://abs.twimg.com/emoji/v2/... draggable="false" alt="🤷‍♂️" title="Achselzuckender Mann" aria-label="Emoji: Achselzuckender Mann">" #issuecomment-716213149">https://github.com/facebook/react/issues/15317 #issuecomment-716213149">https://github.com/facebook/...

For years I spewed nonsense on this website about how Facebook owning React was a huge advantage: dedicated engineering team, large project that dog-foods it, etc.

I was so wrong.

No community-run OSS project would throw their own ecosystem under the bus like this.

We all wondered what would happen if React started prioritizing what benefited Facebook dot com, over the actual React community, but then never even noticed when it happened.

Seriously I& #39;ll die on this hill. MobX was and is a goddamn pleasure to work with. It& #39;s so good @thekitze occasionally gets furious more people don& #39;t use it.

If the sacrosanct rules of React purity are violated by MobX, then re-think the rules and move in a different direction.

And of course it& #39;s not just MobX. Read the GitHub thread in first tweet above. Tons of other projects chiming in to say they& #39;re affect by this.

The response is still the same: "you broke the rules so meh"

Anyway @preactjs still exists. If concurrent mode breaks your favorite React library, I& #39;d recommend looking there.

I know first-hand how brutal it is to make a library CM-safe, doing everything in effects, etc. It& #39;s fucking hard; your favorite library may not have the bandwidth.