4 ms·

Explain the big picture abstraction differences between this and React in two sentences? I don't care about compiler vs interpreter implementation details.

• 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 that run over and over as needed when state changes.
  • sreekotay 6y ago
    Very cool work! And great performance. Funny - during quarantine I've been playing with the OPPOSITE. A no build, runtime only reactive JS engine... Would love to compare notes - you can check out (very much WIP progress) at https://github.com/sreekotay/reefer https://github.com/sreekotay/reefer It's been only a few weeks of fun... but REALLY interesting problem space. I use a DOM memo-ish approach to help with performance...
    • 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 can work runtime only too but I do put most of my effort on the compiler since I can use it to overcome most of the classic shortcomings of the reactive approach performance wise (and DX wise) with a bit of consideration.