HTMX proved there’s demand for different approaches. It’s simple and clever, but limited. Control logic ends up distributed between HTML attributes...
For further actions, you may consider blocking this person and/or reporting abuse
This is a really impressive deep dive, love how you’ve shown step by step how doors handles reactivity, routing and concurrency in Go without pulling in the usual JS ecosystem overhead.
The Beam abstraction for reactive state especially caught my eye the way it ties DOM updates directly to data changes feels both predictable and ergonomic. It reminds me of LiveView in spirit but with a more Go-native flavor.
Thanks.
The funny part is that I didn’t originally plan for
Beamto be used like this. It provides multiple methods for monitoring the value stream using function handlers, where you need to implementDoorupdate logic yourself.Later, I discovered that I use the same patterns 90% of the time, so I made tiny
doors.Subanddoors.Injectabstractions, and it turned out surprisingly solid.Congrats to you! You did absolutely incredible work - it’s got the potential to be legendary 👏
Thanks. I hope so.
Looks like the template screenshot went missing:
