Ryan Carniato
1 min readApr 5, 2020

--

I never looked very close at it. It’s memory profile suggests it uses an approach similar to stage0, domc, or mikado which use DOM diffing. Solid has more memory overhead because of the Reactive system, it also pays off with deeper nested structures since it isn’t top-down. However, looking at the implementation it looks similar to Solid with calling out reactive signals etc. I wonder how granular the rendering is. More granularity means more memory, but also can mean better performance. It looks like its biggest bottleneck is in creation which is consistent with reactive libraries though. It will be interesting to see how WASM progresses. It’s possible this library will be quite impressive when WASM gets past its current limitations.

--

--

Ryan Carniato
Ryan Carniato

Written by Ryan Carniato

FrontEnd JS Performance Enthusiast and Long Time Super Fan of Fine Grained Reactive Programming. Member of Marko Core Team. Author of SolidJS UI Library.

Responses (1)