Hey friends! I just published a blog “Compose from...

# compose

[Leland Richardson [G]]

Hey friends! I just published a blog “Compose from First Principles” talking about some of the implementation details around compose. Would love to hear your thoughts! http://intelligiblebabble.com/compose-from-first-principles/

[Fudge]

Been waiting for this 🙂

[itnoles]

is Stack is like ListView?

[Fudge]

In Flutter (and in Compose aswell?) Stack is a way to have multiple layers of UI, but he probably meant something like a ListView/Column. Perhaps it would be better to rename it to something else in the post?

[Leland Richardson [G]]

it’s more like LinearLayout

[Leland Richardson [G]]

it is just a simplistic example

[Leland Richardson [G]]

i originally just had class Box : Node() but i wanted something that had one property instead of 0

[mzgreen]

I loved the post, great job @Leland Richardson [G]! Can’t wait for the next ones.

And I learned about Gap Lists 👌

So Compose is like Google whiteboard tree interview questions in action 😉

[Gil Goldzweig]

Great post, it clears up some of the missing information about how it works in the background.

[Leland Richardson [G]]

hey - great question. i’ll maybe make some updates to the blog post….

[Leland Richardson [G]]

the answer is kind of nuanced

[Leland Richardson [G]]

what he was talking about was bringing more state into the tree as components and using them to declaratively describe more of your program

[Leland Richardson [G]]

some people feel differently about this, but this is an area where i very much agree with him

[Leland Richardson [G]]

but

[Leland Richardson [G]]

the way he was doing that in react at the time of this talk was by introducing components that provide information to their children by way of having children be a function and providing the data through the parameters of the function

[Leland Richardson [G]]

this was kind of the only way to do that at the time

[Leland Richardson [G]]

and since then react has added features for something they call “hooks”, which can replace a lot of the use cases ryan was talking about here, without introducing the nesting and strange component classes to do it

[Leland Richardson [G]]

for the use cases he was covering, that is now considered the right way to do things in the react world

[Leland Richardson [G]]

in the jetpack compose world, we have a very similar concept to hooks that we call “Effects”. (for instance, this is what +state { .. } and +onCommit { ... } etc are)

[Leland Richardson [G]]

there are some other talks in my blog that i linked that talk about effects in more detail

[Leland Richardson [G]]

the really interesting thing about effects is that i think fundamentally there are no differences between effects and @composable functions.

[Leland Richardson [G]]

there’s still some discussion to be had on this, but my hope is that the concept of effects go away and they just turn into composable functions instead of a separate concept

[Leland Richardson [G]]

because of the architectural differences between react and compose, this is something that react can’t ever do but i believe we can

[Blundell]

amazing 💯 thank you for the insight