Відео

he/him is crazy

Прекрасно, Варя!

Great intro to statecharts

Solid js is the first real framework I've used since jQuery and it's great. Seems like the obvious choice.

This is the best JS presentation I've seen for a long time. SoldJs is definitly the best thing JS world has seen for a long long time.

9:20 Please, the first line of every explanation on Reactivity should be how it differs from the Observer Pattern.

I think Facebook had an extremely unique set of problems that most people don’t have. You can’t be so simple minded to think that one framework can rule it all.

Timestamps - 12:39 Slide with `createSignal` and `createEffect` implementations. An opportunity to understand how reactivity on SolidJS works. - 16:19 Reactivity with vanilla javascript show up. - 16:33 Apply JSX syntax - If there is a function in JSX component, then SolidJS compiler wraps that component into `createEffect` - 18:02 Make it a component: Counter. - 20:22 Ryan shows that Counter function called only once! And update happens due to effect that updates only `h1` tag text. Counter is not actually a component, it is actually a function. - 20:54 Another evidence of Count is just a function and called just once: using `setInterval` inside and call `setCounter` in timer. - 21:49 Two Counters on same page. - 22:21 What about global state? You can do it, it is just your functions and closures, you can architect as you want. - 22:53 Props drilling example. - 23:45 There is a little bit more than you showed me before. If compiler see function call or an expression - it wraps it into effect. Laziness. - 24:30 Map to DOM nodes. Controlling the flow. - 27:13 - components run once - no hook rules - no stale closures - templates compiles into real DOM nodes - most importantly state is independent from components - 28:56 Component need their Javascript even after server rendering. This is known as Hydration. If we can get rid of runtime components, we can also eliminate hydration.

Setting the record straight - single page apps built on reusable components was a flash novelty, not a react novelty. Flash did this in the late 90's / early 00's expertly.

React started out as a great idea, but with hooks and functional components it just seems that every project I join (or write) ends up an incoherent soup. I never know when components update without reading and understanding every hook. My components are littered with memo, useCallbacks and refs. I'm mainly a React Native dev so it's important to not leak event handlers or have native code run callbacks that don't exist anymore.

Damn man 💯

Ryan throwing shade at React in React event :) . love this.

I love these control flow components! This is one of the things which I like more in angular than react ( even though these here in solid are much more powerful!). Now that this is fixed, and with all these other benefits (I have tried for years to make my angular apps fully reactive!), I can gladly retire Angular. RIP 😄

I think that one really important aspect of it is how this can be ported back to react and preact, as signals did. Preact's approach is the bets of both worlds where it keeps the vdom but encourages using signals instead of hooks, so that the vdom render typically only happens once, but it also avoids needing the <for/> component since that part can still be handled by a real VDOM (if you are memoizing DOM nodes, you have a VDOM regardless of whether or not you admit it).

👍

Facebook programmers made vdom a thing and then tried to make things work around it and big companies adopted it and we're asked to know how it works to use it correctly, what a hell of a world 😆 good job Ryan.

The first half of the video could be named: Why you should consider solidjs :)

Amazing .., talk!!

"Direct" and "indirect" is also called "imperative" and "reactive". Also MVC and unidirectional.

As a person developing in react for the last 5+ years, I have to say it seems solidjs does have superior features/capabilities to react from this demonstration

Dude, @ryancarniato love the talk, and LOVE the Sliders reference

Wow, I didn't expect it to be this good😍 Having the opportunity to work with Ryan on solidjs would be great

I have a library that does this without a compiler :) and can be built by pure esbuild (no plugins, just pure esbuild compile speed). I named my loop component Loop and not For :D. Instead signals uses proxy to watch state changes.

Solid presentation Ryan. And very humble of you not to give the performance numbers of SolidJs vs React. You said that performance can always be optimised but I think that React dug itself into a hole and that only a breaking change can take it out of. Looking forward to see you explore the design space of resumability! In my opinion JavaScript has become too complicated, and we may benefit from a new high level language designed with DSLs in mind (a Lisp??) so that we do not need the huge compilation toolchains of today.

I absolutely love this ryan! What a great talk 😄!!!!

Unfortunetely, I feel like there are not many people who will understand how wonderful is this library. I remember the day when I first put my hands on React, after 10 years of experience in js I was writing a junk code that was in a recursive never ending loop and I couldn't understand why at that time. Then I realize that component functions in react always runs over and over again on props change....That never make any sense for me. Another weird thing on react is relying on props change. Javascript is a language that you can't rely on object comparison without compromising performance...In the world of javascript vanilla and browser everything works really well with events... If that event happens, then I know that I need to refresh or update something. To make any update looking for some change inside a object structure is just a bad idea. Maybe some day we're gonna wake up from this stupid fantasy... But it's alright for hybrid mobile app development... only because there's nothing better yet.

Great talk

4:15

I think David has been teasing us with xState v5 for like 2+ years

Great talk

Hi, how to display 3d .glb files from url in react native app

Damn! This looks cool ! Type safety and No run time overhead !

It was a great conference - full of amazing people!

Thank you for the lesson..

🌟 𝐩𝓻Ỗ𝓂Ø𝓈Ｍ

It was great time to be there and meet nice people 🙏🏼👌🏼 thanks

Great talk.

Okay fine... I'll try out Solid soon. The more code I get to throw out while still maintaining understandability is awesome and it looks like Solid is going to get that done for me :)

Good job, Keb!

first question: can you have an effect with 3 dependencies inside, but it's only triggered when two of that dependencies update? there are use-cases like this, and I don't see if we can handle it here second: if effect must trigger function from props, what's the implications of that? I mean, if we pass that function as a prop, how does Solid know, if function is the same?

Wow, this is awesome and I'm a big Tailwind guy. I'm switching over to vanilla-extract!

2022 :D, I've just started building a project and honestly this is a great overview of how to setup CI | CD

when can we use stylex? i can't wait 🥴

great job, thanks. u make me understand about ci/cd and also now i want to learn presentation like you

Please open source this!

Nice video!! you got a like!, one question, what vscode theme is that? i like it and i cant find it in google

is it possible to get a job as a junior react developer for an international student who studies at Tampere University in CSE? as an international student is it mandatory to learn finnish to get the job ?

That looked absolutely horrific. What sane person would even consider xstate after looking at that counter example? This is the perfect example of over engineering and making simple things complex. Total garbage. XState is a dead library.

Can you please make a video showing how to set up Linaria in a new react project? that would be extremely helpful