Hearing him at 12:30 saying "Only once" when calling console.log is fantastic. The fact that he designed Solid with a familiar API makes him a visionaire. Saying the opposite would be crazy. I really hope Solid will grow as it deserves. Thank you, Ryan.
I abolutely love how simple but yet effective SolidJS is. It's amazing to me that the abstractions that solidjs uses are actually really easy to comprehend. It makes all other front-end frameworks and libraries look really overengineered 😁.
I'm a C++ developer that over the years transitioned into kind of front-end stuff. All web frameworks I've seen so far looks really bloated in the sense that it's clear who wins on the trade-off war between performance and "easier to write code". However solidjs is the first framework I've seen that sounds brilliantly simple without compromising how easy it is to write UI components.
The same way you would in any JavaScript framework? Even systems with event delegation(and Solid does do this as well) still run through DOM APIs. If this comment is referring to some sort of scheduling, you won't find more than a microtask queue in most frameworks. React specifically has been working with prioritized scheduling which can help a bit, but any system like that will prioritize user input so again same situation. So I believe the answer is probably do nothing and rely on Solid's fine-grained performance or debounce, throttle, or even timeslice (we have experimental support for this).
@@ryansolid Hi Ryan, greetings from Morocco. I am now deciding to learn a framework. I have started with Solid but struggle a bit with JSX syntax. Should I go grab some React books or Solid documentation is enough to get my hands dirty ? Thanks,
Hearing him at 12:30 saying "Only once" when calling console.log is fantastic. The fact that he designed Solid with a familiar API makes him a visionaire. Saying the opposite would be crazy. I really hope Solid will grow as it deserves. Thank you, Ryan.
I abolutely love how simple but yet effective SolidJS is. It's amazing to me that the abstractions that solidjs uses are actually really easy to comprehend. It makes all other front-end frameworks and libraries look really overengineered 😁.
I'm a C++ developer that over the years transitioned into kind of front-end stuff. All web frameworks I've seen so far looks really bloated in the sense that it's clear who wins on the trade-off war between performance and "easier to write code".
However solidjs is the first framework I've seen that sounds brilliantly simple without compromising how easy it is to write UI components.
1:25
😂
Make 10 clicks per second on the button... what happens... 40? Event flooding? How do you avoid it... since solidjs works with actual dom apis
The same way you would in any JavaScript framework? Even systems with event delegation(and Solid does do this as well) still run through DOM APIs. If this comment is referring to some sort of scheduling, you won't find more than a microtask queue in most frameworks. React specifically has been working with prioritized scheduling which can help a bit, but any system like that will prioritize user input so again same situation. So I believe the answer is probably do nothing and rely on Solid's fine-grained performance or debounce, throttle, or even timeslice (we have experimental support for this).
@@ryansolid Hi Ryan, greetings from Morocco. I am now deciding to learn a framework. I have started with Solid but struggle a bit with JSX syntax. Should I go grab some React books or Solid documentation is enough to get my hands dirty ?
Thanks,
Cool library! Less bobbing be the speaker during the talk would be helpful, the constant back-and-forth movement was super distracting :/
Look up stimming.
If "no bobbing" is more important than content quality and expertise in 2022, I'm really worried about the future...