mobx.dart VS molecule

I'll also add that the MobX documentation is a great resource and much better than explaining than I am. If you want to explore a little more I definitely recommend checking it out.

The native way of state management in Jetpack Compose is `mutableStateOf` and `derivedStateOf`. It is an analogue of mobx.dart. Are you familiar with these concepts? What issues did you face with?

· MobX– It’s a popular technique since a long time and uses Observables, Actions and Reactions to notify the widgets of changes. It as initially designed to be used with JavaScript projects and then migrated to Dart to be used used with Flutter projects. It’s an annotation based package which generates the code using a separate package. Read more about it here.

For more examples and guides you can see the original documentation.

Having said that when it came to testing I did not find a good way to write the kind of tests I wanted, although the documentation for mobx in in Flutter is great https://mobx.netlify.app/ I found it lacking when trying to figure out how write robust unit tests. Luckily I found quite a nice approach that I'd like to share in this post.

MobX ⇨ State Management

Active development: low Github link

Meanwhile, https://github.com/cashapp/molecule and https://github.com/slackhq/circuit/blob/cfcb6e6a28c53c0715d961917a9a5a9ddc07d5f3/docs/presenter.md?plain=1#L18

Reddit uses Molecule, not Circuit.

You could look at Compose, how the Compose compiler works internally, and perhaps build something unique / non-ui or investigate some other deep aspect of Compose compiler.

Thanks for the links, I already opened a bug issue : https://github.com/cashapp/molecule/issues/136

Today in "HN never used a reactive framework that is not React and is offended when UI is not written with Dear ImGui".

This is literally the exact style of SwiftUI and Jetpack Compose (down to the author having used the term fragment, I sure hope this isn't leftover trauma from being an Android developer), except written in Rust (hence having to deal with lifetimes in the middle, default parameters, lambdas being quite verbose and needing to move things, etc).

Not blocking the UI thread is mandatory if you ever want to make any kind of complex UI. If you're a web dev, well you only have one thread anyways, good luck, if you're on any other platform, interactions _cannot_ ever block the UI (unless you, yourself, update the UI to say it is blocked). Making this async is a good thing.

Stack traces are a problem, but then again they've been a problem in any remotely capable UI toolkit.

With ReactiveCell, it looks surprisingly similar to what Compose does, where modifying a State causes recomposition of everything observing it. Which means that it might be powerful enough one day to do the same things as Molecule (https://github.com/cashapp/molecule), or ComposePPT (https://github.com/fgiris/composePPT), where everything is a potential target and it interops really well with existing toolkits.

Hmm, I see 0.4.0 https://github.com/cashapp/molecule/releases/tag/0.4.0

Here's an example: https://github.com/cashapp/molecule

Recently, Cash App introduced Molecule and suggested that Jetpack Compose can help solve the problem of managing UI state.