42 likes
·
13.0K reads
8 comments
It would be great if u explain the need of now destructuring props in solidjs , from what i know , they are using some proxies to track down it , so ...
reference - docs.solidjs.com/guides/getting-started-wi…
To make accessing prop values work with the reactivity, Solid, under-the-hood, uses proxies with getters and setters. This means that if you access a reactive value outside of a solid.js tracking scope, the reactivity is broken: solidjs.com/tutorial/props_defaults
Seems much EASIER than React IMO - your dropping some of those concepts that seemed to me not only unnecessary but maybe uncalled for and solid.js seems to be the answer to some of those.
I'm digging deeper into this - although React has retrained my brain in many concepts (primarily to think in jsx / componential separation) I think solid.js will solidify some of these concepts into a cleaner structure within the code. We shall see.
I vote MORE Solid.js write ups like a part two of this one!! Like this if you agree!! Thanks so much for this! MORE content like this please - your way of breaking it down in comparisons' is much easier to grasp the concepts here and I'm diggin it!
Thanks so much. I would love to do more. Look out for it soon hopefully
I've been interested in checking out Solid more and more. Thanks for sharing!
Great article! I love Solid.js and hope it skyrockets in popularity and usage.
Just FYI your first example in the Gotchas section is missing the ref.
It should be:
<input ref={myInput} />
Thank you, It is fixed in the example
Didn't know it'd be that familiar to react.