compose-samples VS molecule

check this out : https://github.com/android/compose-samples/tree/main/Crane

Basic understanding of Jetpack Compose.

The compose-samples repo has a comprehensive list of samples ranging from low to complex projects which might be worth a look.

And what was learned from Flutter has produced something I consider even more interesting: Compose UI (https://developer.android.com/jetpack/compose) and JetBrains' Compose Multiplatform (https://www.jetbrains.com/lp/compose-mpp/)

Now, same story, in the current documentation the list is replaced by a single UserMessage without any explanation of the previous example. It just says "For a more advanced use case, displaying a list of user messages on screen, check out the Jetsnack Compose example." .

As for the strange infix syntax, you're correct - it's not important (for Dart anyway). Kotlin supports writing code that have DSL like syntax making things like typesafe HTML or Jetpack Compose possible.

Sample apps

This is what Jetpack Compose according to the Android Developers team;

Reddit uses Molecule, not Circuit.

I don't think this is strictly true, the Molecule library allows you turn @Composable logic into a Flow that you could use to render whatever UI you want. I think Jake even mentioned they were using molecule to drive legacy XML based views in parts of CashApp.

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

This link here helped me to understand it way more than the blog link in this post.

Isn't this what Molecule wants to solve?

There's also CashApps Molecule which just builds off the existing state management tools in Compose. I haven't played around with it yet but it looks cool.

Compose itself can be used by pretty much anything then. There's Compose UI, there's Compose Multiplatform, that on the web targets the DOM, on Windows targets... WinUI or any component library ? and more. For example, you can have a terminal renderer with it: https://github.com/JakeWharton/mosaic. Or hell, even drive an iOS view (https://twitter.com/jakewharton/status/1399561083204026369). The way it works also allows transforming coroutines calls, which are asynchronous into basically synchronous components, without ever making use of the UI part (https://github.com/cashapp/molecule).