ryansolid

13 ms·

61.
Components Are Pure Overhead in JavaScript Frameworks(ryansolid.medium.com)
11 points by ryansolid 5y ago|0 comments
62.
by ryansolid 5y ago
Core team on Marko and author of Solid. Vite is exactly the sort of project we've been looking for. Sure I love coming up with the perfect Rollup setups to produce the smallest application bundles. But Vite closed the loop we were look
63.
by ryansolid 6y ago
This comes down to React ships post compiled assets generally and Svelte libs send precompiled. This makes it much easier on library authors but also is because Svelte has built in solutions. This has tradeoffs on flexibility. Now you can b
64.
Fluurt: Re-Inventing Marko(medium.com)
2 points by ryansolid 6y ago|0 comments
65.
by ryansolid 6y ago
I remember thinking when I first saw Marko it's kinda crazy how unknown Marko is given how well they've been doing streaming SSR and Partial Hydration for years. At production scale at eBay.
66.
by ryansolid 6y ago
Does Elder do SSR or only SSG? It's sort of crazy how automatic partial hydration is in Marko. You just write your code and it works. No extra consideration etc.
67.
by ryansolid 6y ago
It's worth pointing out MarkoJS it was basically made for this case for eBay's eCommerce solution. It predates the Next.js of the world but offers similar experience except it's MPA first mentality with seamless isomorphic ex
68.
SolidJS: The Tesla of JavaScript UI Frameworks?(medium.com)
1 points by ryansolid 6y ago|0 comments
69.
How We Wrote the Fastest JavaScript UI Framework, Again(medium.com)
5 points by ryansolid 6y ago|0 comments
70.
by ryansolid 6y ago
I'm big on read/write segregation and explicit mutation. With simple signals you have this naturally. Once you move to a nested tree you can lose this. Keeping this control allows us to adopt immutability patterns and enforce unid
71.
by ryansolid 6y ago
As is probably evergreen browsers to use all features. I use proxies which are notoriously hard to polyfill. It is possible to avoid them but I was not taking IE in mind after that. So while possible to support older browsers with Babel unc
72.
by ryansolid 6y ago
You can use HyperScript(createElement) version. You just forgo the advantages of compilation - better dx(less need for explicit wrapping), better performance(optimized code path), and smaller bundle size (more directed code). Solid's J
73.
by ryansolid 6y ago
Volunteering?
74.
by ryansolid 6y ago
I have the article for you: https://indepth.dev/finding-fine-grained-reactive-programmin... It's a bit dense at times but I try my best to cover the whole spectrum and how it relates to familiar libraries.
75.
by ryansolid 6y ago
The reactive graph is a push/pull system as it updates similar to MobX. This is a great article on the subject: https://hackernoon.com/becoming-fully-reactive-an-in-depth-e...
76.
by ryansolid 6y ago
I think Hooks are genius truthfully. But they are definitely shoehorning something into a place that didn't expect it. You are calling these render functions with the purpose of creating new transformations every cycle, and the injecti
77.
by ryansolid 6y ago
Yeah I guess I mean more I don't understand what it takes mechanically to support those types of transitions. It makes sense to me but I also feel like there would be a lot of details in a generalizable solution. Super interesting thou
78.
by ryansolid 6y ago
It's not unexpected at all. I've had several template library writers reach out to me about the potential here. And there is some. The challenge is figuring out how to hide the reactivity in a way that your end users would be happ
79.
by ryansolid 6y ago
Yep. I agree in practice Solid has some work to do here. The basics are think are reasonable in that we are dealing with your expressions in the template and real DOM nodes. So just drop a breakpoint in that sucker. Sort of return to how si
80.
by ryansolid 6y ago
Yes and keeping the order of application. I actually played with this for a bit. Early Solid let you basically codify mutations you could send in as data. I thought it was interesting to do something like Redux where instead of producing th
81.
by ryansolid 6y ago
It comes down to control and immutability. I know not everyone agrees with this but I believe it's fundamental. You can use the "Immer" syntax of setState if you want: setState(s => { s.list.push(data); }); But in some cas
82.
by ryansolid 6y ago
Awesome I think so too. I love exploring this space in general. It's really interesting to see how you can model problems this way. Reactivity isn't a solution to a single problem but a way of modelling any problem Solid actually
83.
by ryansolid 6y ago
I agree completely. I left an early github issue open with some examples. It just isn't my forte. I've worked with frontend guys who were mostly CSS ninja's and we never relied on framework mechanisms beyond applying some cla
84.
by ryansolid 6y ago
Yep more or less. I was working with Adam, Surplus' author, for a bit before he didn't have time to work on the project further. I've take a different tact now with the reactive system and improved the rendering technique a b
85.
by ryansolid 6y ago
We use JSX identical to a Template DSL more or less. We don't use JSX at all like React does. That's why Solid so performant. It does similar thing to Svelte. We don't compile it into HyperScript. You can copy and paste html
86.
by ryansolid 6y ago
I mean it's basically the same thing as you do with React. You create lens functions more or less to handle get/set over the state object. Solid's setState has a lot more capability than React's handling nested updates w
87.
by ryansolid 6y ago
Yes you are correct. Use diffing here actually very similar to VDOM libraries. It was more performant(and consistent) than just propagating the change purely through manipulation of a proxy. Especially if you consider things like batching.
88.
by ryansolid 6y ago
Generally implicitly either through proxy or get method read. Solid provides an explicit API as well.
89.
by ryansolid 6y ago
Yes it's all the same thing. Your data is reactive and an be modularized. The renderer is reactive with the DOM basically being a side effect. There basically is no renderer just a reactive system with different types of data. It means
90.
by ryansolid 6y ago
I do return a proxy. It's just readonly. I really like the unidirectional data flow and explicit read write segregation of react. This adds so much control without having to add Framework like control mechanisms. I know it isn't e

More ›