We get a boilerplate-free API where shared state has the same simple get/set interface as React local state (yet can be encapsulated with reducers etc. if needed).

createState and createSignal are improvements over React's useState as it doesn't depend on the order of calls.

The equivalent ways in functional components using Hooks:In a state variable: useState or useReducer. Updates in state variables will cause a re-render of the component.In a ref: Equivalent to instance variables in class components. Mutating the .current property won’t cause a re-render.

even without loop we have limit on "useState"

const forceUpdate = () => useState(0)[1];

But what about useState? it used whenever we have some variable that whenever it changes, we want to re-render our component and show some new contents.

I’m here to convince you that when wrapped in a 4 line custom hook, useState can be just as powerful as, if not more powerful than, useReducer when managing complex state.