jetc.dev Newsletter Issue #9
Change is the only constant. So, this week’s newsletter points to Slack threads on configuration changes and compiler changes. Plus, we look at JetNews, getting feedback, and (a) certain doom.
One Off the Stack, One Off the Slack
You’ve got questions. That’s understandable!
Unfortunately, there were no good Stack Overflow questions in
the android-jetpack-compose tag
this week, so let’s look at two interesting threads
#compose channel in kotlinlang Slack!
Note: to view these, you need to be a member of the Kotlin Slack workspace — sign up at https://slack.kotlinlang.org/!
The apparent objective is to allow apps to disable configuration changes for Compose-based activities, with automatic recomposition occurring on a configuration change. Whether this winds up working in the long run has yet to be determined.
Because Compose depends on a particular compiler plugin, Compose is running behind Kotlin itself in terms of versioning. In this thread, Adam Powell discusses the sorts of things that can get unlocked once Compose is able to support Kotlin 1.4, including coroutines support.
Posts, videos, and other new information related to Jetpack Compose!
100% pure code!
…And One More Thing
As the “hey, we have no Stack Overflow questions!” point makes clear, the amount of material that the community is creating around Jetpack Compose is modest. Some weeks, I struggle to fill in all the sections here. That is to be expected, as only so many developers are doing work with early-stage Compose.
I will be starting to write more long-form Compose material, hopefully as soon as next week. And, as Compose matures, and more developers “hop on the bandwagon”, this newsletter will continue to expand.
If you encounter problems in subscribing, let us know!