It doesn't let you write generic components that you can use across all fx's, it just lets you use the same limited state API to set state in different fx's. Mo

It doesn't let you write generic components that you can use across all fx's, it just lets you use the same limited state API to set state in different fx's. Most of the effort with porting code amongst different fx's is refitting your logic into their different component models. So instead of using the well-tested, documented, native reactive model in each FX, yo'd be limiting yourself into using a limited, non-standard state wrapper API. I don't see any value in this abstraction myself. Forcing myself to use it would generate more abstraction/boilerplate in refactoring out custom logic so it's not tied to any FX. If you want to write code that targets multiple JS fx's you're better off with a well thought out proper solution that lets you develop components that you can use in all major components like https://stenciljs.com https://stenciljs.com or alt solution that lets you target Web Components.