molecule VS architecture-components-samples

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.

https://github.com/android/architecture-components-samples/ was historically better

uh, maybe https://github.com/android/architecture-components-samples/tree/a87535608564103423415baddb1e586f0337be44/LiveDataSample/app/src/main/java/com/android/example/livedatabuilder

But Google invented a set of guidelines in "Guide to App Architecture" in 2017 which you can see here in action that after the re-org the new devrels didn't really understand so they ended up making their own version of "clean architecture" where the data layer depends on the domain layer and not vice versa, + never learned how top-level layering like this doesn't even scale ever and they should be creating components, not "layers".

5.) check the https://github.com/android/architecture-components-samples/ repo for samples (if it is a Google library, and only for some things)

When I take the advanced navigation project and update it's dependency to navigation 2.4.0 we get the working backstack as shown here.

That's still an issue .

Hey guys, Im trying to recognise more about api calls in a contemporary architecture. I am using retrofit with livedata/coroutines to make my api calls, but I'm struggling with error handling. Most of the solutions I find, even in googles own example, includes writing a wrapper around your api request and handle the error that. It seems overly complicated and frankly stupid to do something like that for, what I consider at least, rudimentary functionality. Even with Dart/Flutter, google has made this easy ‏‏‎ with async/await and Futures. Am I being lazy to think that if even google needs to write extra code to solve a common use case, they should probably add it to the framework? I dont know, maybe I just needed venting.. what do you think? google's project: https://github.com/android/architecture-components-samples/tree/master/GithubBrowserSample

/uj if you're reeeeaaaalyyyy interested, I found them here lol