And depending on where you are coming from the reactive primitives may take some getting used to (I was already somewhat acclimatized due to my RxJS, Vue, and Svelte exposure) but none of that is insurmountable.
Though apparently some React devs are allergic to the <Show /> and <For /> components (I think they're an improvement as I do tend towards a template style).
Interestingly Rich Harris ended up explaining how SolidJS works…
Rich Harris
@rich_harris
@RyanCarniato why? because conceptually, the Solid compiler is prepending each {...} expression with `() =>` — when you see it like this instead, everything starts to make sense:
return <div>Count: {() => count()}</div>;
const c = count(); <div>Count: {() => c}</div>
21:06 PM - 18 May 2022
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Don't get me wrong, the first hurdle for React devs is the whole render (React) vs. setup (SolidJS) function as a component thing:
And depending on where you are coming from the reactive primitives may take some getting used to (I was already somewhat acclimatized due to my RxJS, Vue, and Svelte exposure) but none of that is insurmountable.
Though apparently some React devs are allergic to the
<Show />
and<For />
components (I think they're an improvement as I do tend towards a template style).Interestingly Rich Harris ended up explaining how SolidJS works…