Recomposition in Jetpack Compose

[@armagancivelek9926]

There is some misunderstanding, for example at 23:45 when we examine the Text composable we can see it managed to skip from the recomposition even though its value has changed, but this is just an illusion. When the recomposition has started ( because of the changing dataPointOne which is a STATE ) whole code snippet is relaunched from scratch and dataPointFour's value is assigned as "oioin". Finally, variable dataPointFour has the same value as the beginning. That is why Text Composable was able to skip the recomposition. If the dataPointFour variable got held the outside of the Composable it would be observed that the Text Composable would not escape from recomposition. The whole description above means the point is not about that dataPointFour is String, it is about the dataPointFour variable's value.

[@toystoryscarymovie-forkids3323]

funny how there was no comment. i didnt understand jack! and it wasnt relatable