Discover and read the best of Twitter Threads about #mobx
Most recents (3)
Perfect State Manager should:
- Batch changes
- Collapse doubled dependencies
- Reuse moved dependencies
- Skip eval which result isn't needed
- Skip eval when dependencies isn't changed
- Eval dependents only when actually changed
- Apply side effects only once on state change
- Batch changes
- Collapse doubled dependencies
- Reuse moved dependencies
- Skip eval which result isn't needed
- Skip eval when dependencies isn't changed
- Eval dependents only when actually changed
- Apply side effects only once on state change
@mweststrate #mobx is too wasteful of memory. I think this is the reason why it is not very fast. You can steal this idea to dramatically reduce the number of memory allocations:
mol.hyoo.ru/#!section=arti…
mol.hyoo.ru/#!section=arti…
🦄I have created so many #free #YouTube #courses that even I've almost lost count! Here is a list of all my courses (#Flutter 💙, #Rust 🦀, #Python 🐍, #Django), with explanations and links! A #thread 👇🏻
Free #Full-#stack Course
In this course we will create a backend with RESTful API endpoints together with JWT token authorization using Django and Django REST Framework to serve our Flutter and Rust clients (This is an ongoing course) youtube.com/playlist?list=…
In this course we will create a backend with RESTful API endpoints together with JWT token authorization using Django and Django REST Framework to serve our Flutter and Rust clients (This is an ongoing course) youtube.com/playlist?list=…
#Riverpod 2.x #State #Management Course for #Flutter Developers (17 hours long course)
In this course we will develop a fully functioning Instagram application with Flutter and Riverpod where users can upload photos, videos, comment, like and more!
In this course we will develop a fully functioning Instagram application with Flutter and Riverpod where users can upload photos, videos, comment, like and more!
#MobX or @recoiljs? Saw a lot of questions on whether they're the same, so a quick thread. First of all, Recoil & MobX solve the same problem: efficient render widely shared state. This is a problem React (Context), Redux and most state management libs don't solve.
In that regard they are very similar. Hence terminology aligns: atoms, dep trees, derived data .Roughly speaking Recoil offers observable.box + computed + useObserver from MobX. A difference is that Recoil builds on React primitives, the benefits are clear:
Leaner, more easily compatible with concurrent mode, piggy back on React's batching. MobX in contrast is more general purpose and can be used in non-React projects and is even ported to different languages (eg Flutter) & doesn't need a React context to work or organize effects
