A modern programming language that makes developers happier.

kotlinlang

I have one question related to Continuing Explorations slide from I/O talk. Does *multithreaded layout* mean possibility of having multiple UI threads? :thinking_face:

I think it mean something like Litho’s asynchronous layout <https://fblitho.com/docs/asynchronous-layout>

I think there is a lot to explore in the space, and we know we want to go in that general direction, which is mostly what I was trying to communicate in that slide.

Does litho do multi-threaded layout or single-threaded layout on a different thread?  We've been thinking about doing multi-threaded layout, because there are many cases where subtrees can be calculated independently and therefore parallelized.  Then, we would have a single UI thread apply/draw the updates at the end.