Tiny little issue with your second solid example description: you used props.count as an accessor instead of a value, which would allow destructuring from props, since the getter is immutable and will not lose its reactivity. However, it is encouraged to use the value instead and avoid destructuring completely in order to avoid errors.
Also, you only showed the parts of solid with a direct equivalent in react, but even though it is much smaller, it comes with even more versatile state management tools: stores (with produce and reconcile, which allows immer-like states) and mutables (to have state objects like in Vue).
Lastly, react provides it's users with some really good debugging tools (which unfortunately are necessary, because the constant re-running of components render normal developer tools almost unusable), while solid can be debugged using normal dev tools; the compiled sources are surprisingly readable.
Apart from that, it's a really well written comparison. Thank you!
Tiny little issue with your second solid example description: you used props.count as an accessor instead of a value, which would allow destructuring from props, since the getter is immutable and will not lose its reactivity. However, it is encouraged to use the value instead and avoid destructuring completely in order to avoid errors.
Also, you only showed the parts of solid with a direct equivalent in react, but even though it is much smaller, it comes with even more versatile state management tools: stores (with produce and reconcile, which allows immer-like states) and mutables (to have state objects like in Vue).
Lastly, react provides it's users with some really good debugging tools (which unfortunately are necessary, because the constant re-running of components render normal developer tools almost unusable), while solid can be debugged using normal dev tools; the compiled sources are surprisingly readable.
Apart from that, it's a really well written comparison. Thank you!
Thanks for pointing out the issue and feedback.