Spent some of the weekend playing with an idea for...

# compose

[Zach Klippenstein (he/him) [MOD]]

Spent some of the weekend playing with an idea for a state management solution that takes advantage of all compose’s handy tricks. This was my first time playing with KSP and I didn’t bother trying to make it pretty, but I have a working demo enough to get a feel for it. I am pretty sure this violates some Compose best practices too 🙈

Anyway, maybe there’s some parts of this that could be salvaged for a real library.

https://twitter.com/zachklipp/status/1361472794312105987?s=21

https://github.com/zach-klippenstein/compose-model

[Tash]

This is really cool @Zach Klippenstein (he/him) [MOD]!! Been meaning to play around with KSP; curious, what was your experience like with the KSP API?

[Zach Klippenstein (he/him) [MOD]]

It’s pretty great. Kdoc on most things, and supplemented with the docs on GitHub it was really easy to figure out.

[Zach Klippenstein (he/him) [MOD]]

Compared to the psi and Android lint apis, everything more or less did what I expected and so it felt a lot more productive.

[Colton Idle]

@Zach Klippenstein (he/him) [MOD] This is awesome. Good work!

[Zach Klippenstein (he/him) [MOD]]

I think the ergonomics are promising. I’m really not thrilled about the complete lack of compile time safety around heterogenous Applier types, and it sounds like beta has been cut so I don’t think there’s gonna be any fix for it. Really too bad, it limits the number of different practical uses for compose in a single codebase.