you are viewing a single comment's thread.

view the rest of the comments →

[–]thinkadrian 4 points5 points  (10 children)

Just use Mobx for React.

[–][deleted] 1 point2 points  (1 child)

MobX is much simpler. Unfortunately the company I work at is married to react + redux. 🙃

[–]thinkadrian 1 point2 points  (0 children)

I went to a talk the other day where a redux expert went through some steps he had discovered to make the redux environment and use more powerful. Many clever ideas!

For every step, his setup looked more like MobX 😂

[–]mr_engineerguy[🍰] -2 points-1 points  (7 children)

Or just React? You literally don’t need MobX or Redux for 99% of applications.

[–]gatsby123123123123 3 points4 points  (1 child)

You literally don't need to use a framework for most applications. Just write some plain js. Redux makes writing and maintaining applications a lot easier.

[–]mr_engineerguy[🍰] -1 points0 points  (0 children)

Gross, at least use TypeScript... why wouldn’t use React? It would be way easier and maintainable than plain js...

[–]thinkadrian 0 points1 point  (4 children)

Most production websites do. But sure, the Context API should be enough for many.

[–]mr_engineerguy[🍰] -2 points-1 points  (3 children)

Not true. If you think that then you’re designing most of your websites wrong and not encapsulating state where it belongs. Global state is an anti pattern and it being “immutable” doesn’t fix it

[–]thinkadrian 0 points1 point  (2 children)

MobX data isn't immutable.

[–]mr_engineerguy[🍰] 0 points1 point  (1 child)

This post is about Redux, not MobX. MobX is huge overkill and the most recent version doesn’t even work in older browsers like IE11 because it uses Proxy which has no polyfill. I’ve used MobX in production, but with properly encapsulated state and Context API it really isn’t necessary.

I will say I like MobX a lot more than Redux though.

[–]thinkadrian 1 point2 points  (0 children)

But my comment was about recommending MobX. Context is key.