4 ms·
> It just basically does everything React does but better SolidJS still has some major pain points; the one I found was not knowing whether a prop was a signal
by ironmagma 1y ago
> It just basically does everything React does but better
SolidJS still has some major pain points; the one I found was not knowing whether a prop was a signal or needed to become one. The type system doesn't help much. In React, you know for sure that if your reference changes, the component reading that reference as a prop will re-render. In Solid, it's less clear whether the update will be observed.
- deleted 1y ago[deleted]
- mexicocitinluez 1y ago> In React, you know for sure that if your reference changes, the component reading that reference as a prop will re-render. Amen. Data flows down. That, to me, is one of React's biggest strengths.
- uzy777 1y agoAmen because of this we have useeffect and calling the whole component tree on a isloading change
- ironmagma 1y agoisLoading should be a boolean; it will maintain referential equality across renders and not cause a re-render unless it is an actual edge from false to true or vice versa.
- mexicocitinluez 1y agowhat? what does what you said have anything to do with what I said? how does "data flowing down" now related to the use effect dependency cycle? are you new to programming?