I've thought many times that maybe we should add it back in now that people understand state a little better. But I'm not convinced that my original reason for removing it doesn't still hold

Yeah I agree with this. Often when I'm writing my own code using it I'll feel this desire to define the convenience api, but usually I think: well, since it's not standard, people reading this might not know as quickly what this is. Prioritizing for the reader rather than the author.

I guess not... Kinda sad when you see it paid out like that lol🙃

Thanks, Amanda!

I deleted the original `state` API in compose because so many developers were missing that `mutableStateOf` did not need to be called in composition, opening up many doors to more elaborate state handling.

I'm always surprised that I don't see the simple one-liner convenience function defined more

I'll be joining @anthropic.com in a few weeks. I'm excited to be working on something challenging and new!

Dad life indeed. I've just got the one. Turns three in a few weeks. How old are yours?

Hey! Currently hoping that reintroducing some twitter-like thing into my life isn't a mistake. How have you been?