ryansolid

14 ms·

91.
by ryansolid 6y ago
I agree. I would love to do more. The truth is there is just so much to do. It's hard to find a balance between writing cleaner docs and say solving Async Hydration with Suspended Components. I had the luxury early on to prioritize the
92.
by ryansolid 6y ago
Correct. The idea is that the derived state only updates when the underlying state updates. And the mapping to the DOM is just derived from that derived state. So list updates.. triggers bubble sort, triggers DOM reconciliation. The differe
93.
by ryansolid 6y ago
> In the JS framework benchmark suite, SolidJS and InfernoJS performance is almost identical (with SolidJS having a much larger margin for error in most tests). I mean I agree with most of your post, but I'm not sure I would necessa
94.
by ryansolid 6y ago
Thank you as always. Early days spent so much time justifying things, everything became these expositions. Time to tighten up.
95.
by ryansolid 6y ago
Thanks. I get criticism like "Why even make this? just use React." But it's so different. Yet I didn't want to throw everything away. People forget React came up when there were tons of libraries with similar reactive ap
96.
by ryansolid 6y ago
It's easier to just open up and debug than say VDOM views since you can see your dynamic expression (what's not updating) and just drop a breakpoint. The template structure flattens so you don't have this issue of nested chil
97.
by ryansolid 6y ago
At that point you remove the benefit of the compiler but that is fine. You are essentially writing a builder script like VDOM HyperScript. But it isn't like there isn't a runtime portion, it just that it can be smaller due to tree
98.
by ryansolid 6y ago
With React your Component re-renders over and over and your Hook dependencies explicitly whitelist change. With Solid your Component is a basic function that executes once closing over state getters with its Hooks, which are the only thing
99.
by ryansolid 6y ago
Yeah JSX has its clear advantages. But I wanted to offer runtime only solutions as well. Tagged Template Literals is still the best runtime only solution for Solid, but I've got HyperScript too. Just remember it's reactive so wrap
100.
by ryansolid 6y ago
Thank you for your kind words. It can a difference to have the kind words of a few strangers. I'm used to these sort of responses now. And welcome it to a certain degree. Insightful comment can lead to interesting discussion. Ignorant
101.
by ryansolid 6y ago
Warning performance there isn't stellar there yet but it is my current active area of research.
102.
by ryansolid 6y ago
There is an open issue for this. It's an area that needs work since I can't just repurpose existing tools like VDOM libraries do. The challenge that comes with pioneering an approach.
103.
by ryansolid 6y ago
It can be used with MST with a bit of interopt. As for native it's possible but would require different compiler output. I saw an approach with another library mind you that emulated DOM API over Native script and used the same compile
104.
by ryansolid 6y ago
I read that article a few weeks back. It's interesting. I see the desire to lessen on tooling but it is going to be hard to match what these libraries are doing purely runtime. I know people want to get there again. But I think we are
105.
by ryansolid 6y ago
I've been working in this area. Solid now has string rendering on the server without DOM emulation. I'm just one person so I went with what was cheapest first.
106.
by ryansolid 6y ago
Probably. I lifted it from React when I opened sourced the project because I liked how generic it was.
107.
by ryansolid 6y ago
Sort of. I don't think you can write off the virtual Dom. But this is basically my area of research. I'm saying that a specific approach to reactive programming is more performant. I have an article for that too: https:/&#x2
108.
by ryansolid 6y ago
I agree. I love that about React. I think all UI libraries could learn a ton from React. https://medium.com/@ryansolid/what-every-javascript-framewor... But it isn't something that completely gets abstracted. There
109.
by ryansolid 6y ago
It's interesting to wrap the persistence in there as well and it's lightweight so that's a plus. But someone also could use say Redux(or Storeon) and achieve a similar thing. The challenge of interopt is more with conflicting
110.
by ryansolid 6y ago
Solid doesn't re-render Components over and over.. so integrating React is as simple as wrapping a `createEffect` calling `React.render` on a ref. The other way around is a bit harder, but been at this for a while here is a codesandbo
111.
by ryansolid 6y ago
Web Components were what originally led me to keeping the Component side light in Solid, which eventually influenced some of optimizations in that area. I hope you find things have progressed nicely in the last year.
112.
by ryansolid 6y ago
Don't worry I didn't find the initial comment rude. I get what you are saying and I respect not everyone has time to read a 9 min article. Just know that I'm very aware of it and reflect on it in that article and a lot of wri
113.
by ryansolid 6y ago
For sure. Which is why in the early years I just did my thing. Win the benchmark battles and move on with my life. But then this whole React Hooks thing came about. And Vue Composition API. Even Svelte 3, and I was like.. there is a better
114.
by ryansolid 6y ago
Feel free to shoot any issues or discussions on our gitter or reddit. You are correct because it doesn't work like that. It works more like MobX. There is no render function that runs repeatedly. Instead everything is split apart granu
115.
by ryansolid 6y ago
Fair enough. Keep in mind I've been working on this for close to 5 years. Basically around the time I realized KnockoutJS was going to die out and React was for good reason going to win. Here is an article about why this library exists
116.
by ryansolid 6y ago
No Hook Rules. Hooks are an amazing feat by the React team as they basically come so close to emulating the behavior here with running through top-down VDOM reconciliation. But they can't be nested etc.. This reactive approach is simil
117.
by ryansolid 6y ago
That is an interesting project. And looks like they beat me to Solid name by a few years. I usually refer to my project as SolidJS. But thanks for bringing this to my attention.
118.
by ryansolid 6y ago
Here is an introductory summary of SolidJS: https://dev.to/ryansolid/introducing-the-solidjs-ui-library-...
119.
by ryansolid 6y ago
Syntaxually and philosophically. Implemention-wise it's more like MobX or Vue style reactivity without a Virtual DOM. It takes compiled reactivity past the localized component model of Svelte to new(ish.. the library has been around fo
120.
by ryansolid 6y ago
Yeah I think that is the convergence point. Marko actually has a bit of a head start in some ways. But they need to look at the client part which I imagine with users like EBay is less necessary. React is likely getting pretty close, but I

More ›