5 reasons to love Solid

Started to loved solid, when someone in twitter give performance review.

It seems slowly solid will overtake react. I think it lacks support with libraries such as material ui, but once that is achieved i would say it will be no.1

Nice video. One major annoyance though - don’t keep changing the code on screen as you’re explaining it, as it makes it much harder to follow

While react is technically good, I would love to see other frameworks gaining popularity as they are shipping less js and they are going for improved developer experience.
I tried Svelekit and it is awesome.
Will try solidjs.
Thanks for the awesome video.

honestly i wanted to try it seriously but svelte seems to be much more simpler and cleaner code

You conviced me. I'm gonna give Solid a try.

I've never known what a meta framework is. I appreciate how you put it plainly.

I'm really enjoying your solid videos, but would really appreciate timestamps

If they only dropped the terrible functional approach this would be a better preforming version of knockout js. MVU is just a bad pattern hard to deal with it redux helps but having one gigantic state is so hard to work with and requires so much boilerplate code and dealing with immutable references is hard.

Why bother. Svelte is 3KB and improves your life.

👏🏻

i'd love solid and svelte personlay, however i have to force my self to stay in react for obvios reason. i really wish solid will replace reactjs someday.

Hi bro, please do a performance comparison video on solid vs qwik.

Very bad, very hard to a newbie to follow...

I started using solid recently, however, it seems that signals are actually different from states.
I'm kind of stumbling across a wall in that I could not really find a good solution to this other than using switch element.
When I pass a signal to a component as a prop, if I update the signal it doesn't trigger a rerender of the component somehow.
For example, I need to make a switch button to invoke dark mode, but the components don't react to the signal. Even using createEffect doesn't get triggered. Which is weird.
I searched everywhere, tried every solution other than the switch element, nothing works. Using switch causes me to duplicate the same component for every change I make. It doesn't make sense.
The same solution works on react, but it doesn't on solidjs.

Another framework? Considering all frameworks copy each other what's the point in switching once again. Just stick with the framework that uses terminology and syntax that fits your mind. Performance benchmarks are negligible facts in my book , cause if your app approaches benchmark level of workloads you're doing something very very wrong.

I would be a bit careful with using map in solid's jsx (irl and in ur educational videos). Since there is no vdom, jsx translates directly to createElement-calls. so with your example it would re-create the html and remount all the components inside ur map-callback everytime 'members' change. That's the reason why there are control flow components like <For> and <Index> in solid.