Compose-web is mainly focusing on wasm at this poi...

# fritz2

[Jilles van Gurp]

Compose-web is mainly focusing on wasm at this point. And nice as that is, it's not ready for mainstream usage and also limits you a bit in terms of delivering a well designed experience. Compose html is sort of usable but not getting a lot of love and attention lately. They haven't come out saying that it is deprecated just yet. But it is starting to feel like it.

Fritz2 uses kotlin-js and is easy to use if you need to work with existing javascript libraries. Nice if you want to use existing web components. Also the headless component framework that comes with fritz2 is nice. And styling things with tailwind (or similar css frameworks) is pretty nice and easy and a bit more aligned with how the rest of the web does styling. I just think of kotlin-js as a nicer typescript and fritz2 as a nice framework that makes the most of kotlin-js that cuts me loose from the hellscape that is react development.

Fritz2 does not depend on any compose classes but it's not that different in terms of how it works. State is represented using State Flows. The compose compiler kind of tries to hide that. Fritz2 is more explicit about it. If you have a flow, you can react to it by rendering it. Creating them is easy. There's a ksp based compiler for some annotations to make this easier. I'm not actually using that as I don't like having too much compiler magic and the code it generates isn't exactly rocket science or something I need a lot off.