Making Poker with HTMX: Real time multiplayer using SSR with Kotlin, HTMX and Tailwind

I am continuing to explore HTMX with the Kotlin DSL for HTML. I really think this might be the only way I build websites going forward.
I'm pushing it in a weird direction today by building a server side rendered multiplayer game. I'm very happy with the result.
I enjoyed the user experience of using HTMX websocket and HTMX polling. This is a very nice developer experience that lets me build good looking websites quickly. I built this before I started using Tailwind UI but that may be something I look more into in the future.
Software engineering is completely changing and I look forward to a future where I don't have to write JavaScript. Which may be sooner than I expect -- I still need to look into KotlinJS to see what it can actually do.
0:00 - Poker demo
0:53 - Queue demo
1:07 - Explanation
3:03 - Main menu UI
3:37 - Main menu server
4:13 - Queue UI
4:29 - Queue endpoint
4:43 - Game UI
6:48 - Game model
8:00 - Game web-socket
8:44 - Actions menu
9:36 - Final thoughts

[@alexeinunez778]

Can you show the developer experience? Debugging, making changes, seeing the changes update, building, shipping

[@braiso_22]

Hi tom, do you have a github account where I can follow you? I would like to be able to see the code in this repository so I can implement something similar myself.
Speaking of another topic, what do you think about compose multiplatform?

[@tom-delalande]

I don’t have anything public yet. I’m wanting to clean everything up and publish them in the future.
I haven’t used it but from what I’ve seen so far it has the potential to be the holy grail. Writing native source code from a single code base would be a game changer. Have you had a play with it? What are your thoughts?

[@eRatio]

@@tom-delalande Would also be highly interested to see how this is implemented! Looking forward to the publish :)

[@xMadingx]

Same here, would be highly interested in the code or a project getting started video! :)

[@rick_er2481]

Me too would gladly see the code

[@kirillvoloshin2065]

would be interesting to see how winning combinations are parsed)