qwik is a fundamentally different framework for creating server-side-first web applications. It features resumability instead of hydration for making content interactive in the browser. It results in more performant and lighter-weight web applications.
It creates some problems with regards to integrating with certain libraries however. Two other state machine libraries are unable to make a clean integration. There's no way to easily serialize XState machines. And Zag.js usage is blocked because of the way it needs to handle event.preventDefault().
I'm wondering if Robot would consider trying to create an official qwik integration. There's a lot of people wanting a state machine library for usage within qwik applications and Robot could take advantage of this and become the standard for this use case.
qwik is a fundamentally different framework for creating server-side-first web applications. It features resumability instead of hydration for making content interactive in the browser. It results in more performant and lighter-weight web applications.
It creates some problems with regards to integrating with certain libraries however. Two other state machine libraries are unable to make a clean integration. There's no way to easily serialize XState machines. And Zag.js usage is blocked because of the way it needs to handle
event.preventDefault().I'm wondering if Robot would consider trying to create an official qwik integration. There's a lot of people wanting a state machine library for usage within qwik applications and Robot could take advantage of this and become the standard for this use case.
Relevant links:
qwik https://qwik.builder.io
qwik GitHub issue: State machine as first class concept https://github.com/BuilderIO/qwik/issues/1171
Zag.js GitHub issue: qwik integration https://github.com/chakra-ui/zag/discussions/392
Thanks!