Kotlin

i'm running into this weird race condition in my compose screen. whenever the underlying flow emits too fast, my derivedStateOf seems to skip updates or hold onto stale data. is this just me misusing the api or is there a specific lifecycle trap i'm ignoring?

anyone else seeing massive memory spikes with kotlinx.serialization on backend services? switched a few endpoints from moshi and the heap bloat is real during polymorphic deserialization. is it just reflection overhead or are we hitting object allocation limits? not worth the kmp…