Author here. SXO + Reactive Component offers a middle ground between full hydration and static HTML. By rendering semantic server-side JSX and using a 4.8KB client library to provide signal-based reactivity.
I'd love to hear what you think about this approach for web components architecture.
Documentation is an essential part of software development in the open-source world. We all know it's crucial, yet somehow, it always ends up as a collection of outdated markdown files and half-finished README.md lurking in our repositories. That's exactly why Query Docs exists—not to reinvent documentation but to make it actually work for both contributors and developers.
Hey, Query [1] creator here. The article raised some exciting challenges. With Query, we solve booth downsides mentioned in it. To keep things simple, we use EventSource for live reloading [2] and JSX Server-Side Rendering [3] for those who want component reuse in the server. It's just JSX with some helpful extras. I'm happy to elaborate on the technical decisions if anyone's curious.
I'd love to hear what you think about this approach for web components architecture.