molecule VS riverpod

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.

From a library standpoint, I would recommend https://riverpod.dev over any other state management libraries for productivity purposes.

I have the following code. When I hot reload I get an error like this. Apparently this is fixed in dart 3 and Remi mentions a solve here. I am unclear how to refactor my code to achieve the solve without upgrading Flutter to an unstable version (which I've tried and cannot use because of certain render issues).

I saw this official example but it doesn't use riverpod_generator : https://github.com/rrousselGit/riverpod/blob/master/examples/todos/lib/todo.dart

Looking at the riverpod.dev docs, I saw that they were using Docusaurus which led me to creating this site. You can think of it as a guide or your go-to when trying to build gRPC servers and clients using Dart. It's open source hosted at this repo and everyone is really invited to Collaborate.

Riverpod Docs

I think you might need to use a state management if you want to keep the username and email always in scope in your application. Consider using riverpod or provider

You're right, it's Riverpod.

Sources: Riverpod: https://riverpod.dev REST: https://github.com/codeReview-youtube/flutter_auth_api PROJECT: https://github.com/codeReview-youtube/flutter_rest_riverpod_authentication