Ryan Carniato
@ryansolid
got signals? @solidjs.com @sentry.io previously: @netlify.com @markojs.com
Async in frameworks happens in 4 phases: 1. create 2. consume 3. block 4. read The problem? Most fuse 2 & 3. Consumption triggers blocking. This puts DX (coloration) at odds with UX (blocking). Solid 2.0 snaps them to the poles. Colorless logic. Non-blocking UI.
If there was any type of proposal to fall into XKCD I feel templating would be it. Just think of how many JS frameworks exist simply over differences in template syntax. It isn't that providing a standard solves that.
Since people like pictures. I've used this before but this is why I find this direction compelling. I honestly don't have any ambition left of eCommerce. But I don't want to give up anything on the right side.
Thank you everyone who supports the streams. I know my content isn't always the most approachable but the channel has hit 20k subs. So thank you!
Received this in the mail today for my son. I see the @solidjs.com mascot is alive and well. Thanks @davedbase.com!
Some people wanted a copy of the chart from the stream so here it is. If I knew this was going to be controversial at all I would have done this years ago. To me this is pretty straight forward. "Framework Client Render Performance"
I'm happy that users of @solidjs.com seem to be happy with the framework they are using. While it is a very saturated field out there and it is hard to move usage numbers I'm thrilled we continue to be the move loved framework by those who have used it.
I forgot I had signed up here. But it was @wesbos.com who provided me with the most compelling reason to check it out.