The World Beyond Components, by Ryan Carniato

[@seanknowles9985]

Ryan hitting the spot again!

[@osman3404]

OMG what an impressive presentation. I’ve been huge fan of Rx (reactive extensions) but it looks like Solid is one framework that brings the Rx ideas to life. Specially about rending only the changed dom Elements

[@mistersunday_]

I'm only waiting for Solid Start then I'm jumping ship from React/NextJS to Solid

[@jesse-aubin]

It's here in beta and is super cool

[@sinasalahshour]

does anyone know how to implement cleanup function in createEffect function?

[@Pesthuf]

The approach is brilliant. I never liked hooks. It always felt to me like they figh JavaScript at any opportunity. React components completely re-executing, including all your hooks and effects being executed always felt so wrong to me. Why not just use a closure and _not_ have the outer scope re-execute..? And then there's the hooks being married to react's component system, so things that work inside components don't work outside and things that work outside them often don't work inside unless you spend a lot of time optimizing and trying to stop react doing its thing - calling your functions again and again, un- and resubscribing again and again, executing requests again and again - from ruining your application using things like excessive memoizing and deuplexing libraries... Meanwhile, it feels like Solid just does the right thing - it simply doesn't call things that can't have changed. That's like 80% of what you actually do writing react, gone. And you can use its reactivity outside of components the same way you use them in them. Svelte looks more attractive to me because it's opinionated on things like how styles are to be managed and has a great implementation of implicit animations, including spring based ones, but if I wanted something like React without the things that make it awful, I would definitely go for it.

[@sanjarcode]

Hmm, so virtual "state" in addition to "virtual DOM". Brilliant.

[@azulamazigh2789]

this is tempting me to ditch java for javascript/typescript and backend for frontend.

[@mihirdharangaonkar6916]

The problem with this type of talk is limited time given to presenter. You loose the presenter 5 mins after talk starts ,because the speed at which he has to finish the things in given time. This is not good for beginners wanted to learn new framework. This creates unnecessary mental block.

[@lodgin]

To be fair, this isn't a crash course to the library, it's an introduction to it.

[@tui3264]

the speaker has lot of talks in his channel, best thing is his knowledge of other frameworks

[@codedusting]

This is not aimed at beginners anyways. It's for people on the edge of technologies and advanced level engineers.

[@typoerror177]

so it's basically VueJS with react syntax

[@dav_kat]

I say this is Svelte with React syntax.

[@ryansolid]

It's more similar to Vue than Svelte. But it is like neither as it does fine grained rendering. Like the way Solid only updates the one text node directly via effect isn't how either work. Vue generates a VDOM and diffs, and Svelte re-runs component update functions and checks against bit flags. They both have their reactivity but Solid uniquely does fine-grained rendering.

[@kafelinux]

i just move from react to solid.... solidjs speed is amazing....easy than svelte and react

[@linorabolini]

what if ... const [getFriend, setFriend] = createSignal("Bob") May be more clear to identify that getFriend is a function

[@SmartSleeper]

createSIgnal returns a tuple comprised of the getter (getFriend) and setter (setFriend).