[HN Gopher] Preact Signals ___________________________________________________________________ Preact Signals Author : no_wizard Score : 28 points Date : 2022-09-06 20:54 UTC (2 hours ago) (HTM) web link (github.com) (TXT) w3m dump (github.com) | nikivi wrote: | Don't get why you would use it over Solid | (https://www.solidjs.com). I guess to keep compat with React | ecosystem but moving React components to Solid is trivial. Solid | signals have better DX & I think are more performant. | cageface wrote: | I recently ported my side project app from React to Solid and | it was surprisingly straightforward. I think this is an | advantage of Solid over Svelte. The concepts and syntax are | quite similar and it eliminates the manual dependency tracking | headaches from React. | rektide wrote: | Minor aside, I really dig that there is a synchronous | `signal.peek()`. Common accepted dogma is that an async value is | ought only be accessible asynchronously, but having the | capability to do the "you probably shouldn't" thing | (getting/seeing current state synchronously) is, imo, the sort of | escape hatch that adds potential & makes greatness possibility. | | There's a lot of reason we let fear govern language design & | direction, but I really believe we also need to give a lot of | credit to what we make possible (or not) in these decisions too. | For a long time, keeping async & sync separate has been the law | of the land. I hope someday we can see values & their changes | with less of a everything-neatly-in-one-box-or-another view, & | more integratively. | brundolf wrote: | Very similar model to MobX. Main difference seems to be that deep | accesses/mutations aren't (?) tracked, which is unfortunate. But | it does mean there's a little less magic going on. In any case, | I'm glad to see more people doing this style of reactivity ___________________________________________________________________ (page generated 2022-09-06 23:00 UTC)