Could compose web be implemented without a virtual...

# compose-web

[Daan]

Could compose web be implemented without a virtual DOM? Because vdom is one of the reasons why I eschew frameworks like React. It makes development easier but produces slower, more memory intensive applications.

[Daan]

I had no idea Compose is being developed by the people who wrote React! I'm glad you agree with me and are now working on something even better. Compose sounds really interesting, at some point I'm going to take a deep dive and learn how it works internally. Declarative UI is the obvious way forward, but the right way to do it isn't very obvious to me.

[Daan]

Does Compose deal with the issue you have in frameworks like JavaFx with complex graphs of observables and temporary invalid state? In the React world, Mobx for example solves this by explicitly modelling the dependency graph and figuring out the correct order to propagate changes for you.

[jim]

Yes, Compose behaves very similarly to Mobx in that sense.

[Daniele B]

@Daan in Kotlin, state management is made very easy by something called StateFlow. It fits perfectly with declarative UIs, and it’s multi-platform! This means it can seamlessly apply to both JetpackCompose and SwiftUI.

[rsktash]

@jim hi is there any news regarding compose web milestone?

[jim]

Nothing worth announcing yet, but @shikasd is doing some great work continuing to iterate on his CL. You can follow along here: https://android-review.googlesource.com/c/platform/frameworks/support/+/1469369/