ryansolid

9 ms·

1.
by ryansolid 1mo ago
No release announcement has the time to explain how things work. I actually think in hindsight what Rich did by including a video in the Runes announcement worked well. I will have a livestream tomorrow.
2.
by ryansolid 1mo ago
Hey want to see what AI generates when I ask it to talk about Solid 2.0. It's not that. It is: https://hackmd.io/@0u1u3zEAQAO0iYWVAStEvw/rJM9ws3Kbg https://hackmd.io/@0u1u3zEAQAO0iYWVAStEvw/H1
3.
by ryansolid 1mo ago
Like a cold. Sometimes people call an illness a condition. A condition that can happen to you. We have frameworks essentially living in a completely synchronous world--like a 2D plane--and they can't tell that there is another dimensio
4.
by ryansolid 1mo ago
I did write the post. This is better.
5.
by ryansolid 1mo ago
I'm not sure you would, but I actually did this exercise a bit on stream after my last article. To try to show people what I was talking about. I actually ahve a really good example of this on some unreleased stuff that I can't ta
6.
by ryansolid 1mo ago
It's when you go top to bottom reworking parts of an article. Often later changes can impact earlier prose, so often I end up doing editing in several passes. That being said AI decided that term. It's actually more accurate to th
7.
by ryansolid 1mo ago
Because it's important. You don't want to read my raw writing. Try to read my HackMD and you see what you'd get. It's always taken me a lot of work to release my medium and dev.to articles. Grammarly working hard, and mu
8.
by ryansolid 1mo ago
Yeah and I always found that really unfortunate. The truth is the JS Framework Benchmark hasn't really moved more that fractions of a percentage since we first hit the mark 7 years ago. Sure many frameworks have been on their way to ca
9.
by ryansolid 1mo ago
The challenge with this is we released too much at once. I really had a hard time with this announcement because I couldn't fit a full tour in less than a 6 article series. So how do I summarize? I picked up on the async headlines and
10.
by ryansolid 1mo ago
I like my wording for `miss` better but I like the AI ending much better. This was just in a small two sentence response. I find over the course of an article the impact is much greater.
11.
by ryansolid 1mo ago
To be fair the writing has been on the wall for years for those paying attention. I never believed in Metaframeworks and it was this sort of awkward truth we had to deal with because the technology wasn't where it needed to be. SolidSt
12.
by ryansolid 1mo ago
Before: Anyone who has spoken to me knows I talk in run-on sentences. I never complete a thought without interrupting myself. And I write the way I talk. I used to heavily edit that out of my writing, but now AI uses the proper punctuation
13.
by ryansolid 1mo ago
It was human written, fed to AI, human adjusted, re-fed, and around again — for days, with dozens of reviewers in between. (GPT 5.6 Sol doing the AI half of the lifting, for what it's worth.) So "nobody even looked at it" is
14.
by ryansolid 1y ago
Yeah it is an interesting one. There is definitely a slowdown due to the amount of wrapping that happens. These sort of libraries tend to put component in component in component etc.. so there is a lot of prop iteration, Object.keys calls i
15.
by ryansolid 1y ago
Thank you for correcting this. I was going to come and respond when I saw this earlier but hadn't had a chance. Yes the annoying part is not being able to destructure but you definitely don't have to (and it isn't our recomm
16.
by ryansolid 1y ago
To be fair by that metric Vue has the fastest now with its core built with Alien Signals. Raw reactivity benchmarks don't actually show very much because these systems are so fast that the quickest to the slowest reactive library doesn
17.
by ryansolid 1y ago
It isn't necessary. Solid has a similar custom renderer, with Pixi, three.js, terminal, etc... integrations. Solid is actually used a lot in embedded applications since it is low memory and performant. It powers Comcast's TV appli
18.
by ryansolid 1y ago
I'm curious which part of laziness are you concerned with? Is it delayed execution in events? It is just most lazy things run almost immediately during creation anyway, and on update everything is scheduled anyway. The only lazy thing
19.
by ryansolid 1y ago
Ironically, mechanically Vue and Svelte historically were much closer to React. Vue has a similar VDOM and Svelte while compiled still had a rerun component model. It was only the past year about 6 years after Solid showed the way Svelte 5,
20.
by ryansolid 1y ago
I wonder how long by comparison you would have had to wait for React to fix a bug of that nature. Obviously no comparison on maturity given difference of user base size, especially 3 years ago. I appreciate you sharing as I think stories li
21.
by ryansolid 1y ago
Low Commit count suggests nothing other than maybe lower traffic. I've been able to keep issues the main repo under 50 issues most of its life. I admit work towards the next major version has let this slip upwards. Also effort is split
22.
by ryansolid 4y ago
So excited for this. SSR with Astro is a gamechanger which opens up its usage to so many different avenues. Great strides with framework interop too. Named Slots really closing the gaps. And of course any framework where SolidJS can shine s
23.
by ryansolid 4y ago
Yeah RSCs are another approach I'd say that are playing with these sort of approaches. Other notables include: Marko: https://www.markojs.com Astro: https://astro.build
24.
by ryansolid 4y ago
So excited to see what you all have done here. trueadm is the creator of Inferno, and has a great eye for performance. Can't wait to dig in.
25.
by ryansolid 5y ago
It does. Just referential check. Our reactivity is nested and we don't want blow out everything so even though there is read/write segregation and immutable interfaces the internals are mutable. In so sorting looks at referential
26.
by ryansolid 5y ago
It can't. Not in a consistent manner. When diffing user provided immutable data you need a user provided key. Otherwise it can't tell the difference between a new list entry and a nested update. You could treat every nested update
27.
by ryansolid 5y ago
But those dependencies would be static. This goes beyond that. I won't call hooks flawed, they are suitable for React's model, but looking at what reactivity does is a different sort of thing. It is a subtle difference at first.
28.
by ryansolid 5y ago
Mostly except there is no VDOM, the reactivity applies right down to the DOM binding. And it predates Hooks and Vue's Composition API.
29.
by ryansolid 5y ago
Yep. Looks sort of like the Solid example in the article. It's basically my auto-response to Svelte syntax. Once you do anything in Svelte it is more or less the same thing. Just different priorities. In Solid you can take that code as
30.
by ryansolid 5y ago
Or Vue either to be fair. Similar rules in the Vue's setup function. It's how reactivity works in JavaScript. Basically don't destructure or access values out of of primitives or JSX. That's basically the gotcha. Unfortu

More ›