>> The nice thing about Solid is that state is de-coupled from rendering. > Are you referring to the part that solid components "disappear" at runtime? Or that

>> The nice thing about Solid is that state is de-coupled from rendering. > Are you referring to the part that solid components "disappear" at runtime? Or that solid signals can be used outside of components? My mental model of Solid's reactivity is "plain JS". Components are also "plain JS" with a bit of syntactic sugar that auto injects one effect on render. No hook rules etc. That should make reasoning about Solid apps easier (in theory) and we might use the reactivity system outside of UI. In particular, we need to develop a filesystem implementation for the browser that could benefit from Solid's reactivity system. > I looked at that RFC and i found it interesting that Svelte was considered, but Vue wasn't I started my web dev journey with Svelte (coming from Python + Flutter). The first prototypes were built in Svelte. It became clear that Svelte might be too restrictive for a complex SPA. Solid felt/feels like a baby of Svelte + React.