return-optics
react-solid-state
Our great sponsors
return-optics | react-solid-state | |
---|---|---|
1 | 4 | |
13 | 185 | |
- | 0.0% | |
10.0 | 1.8 | |
over 6 years ago | about 2 years ago | |
Elm | TypeScript | |
BSD 3-clause "New" or "Revised" License | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
return-optics
-
Solid.js feels like what I always wanted React to be
Yeah? I wrote something to deal with it too (https://github.com/toastal/return-optics) 5.5 years ago. You arguably chose the wrong data as `(model, Cmd msg, Maybe extMsg)` instead of `(model, Cmd msg, List extMsg)` which would give you more flexibility and still functions as a monoid on [] instead of Nothing, but allows multiple messages shrug. I tried this approach more recently and it involved me having to encode all of actions in a massive tree and then I still had issues with certain messages including now having to UUID all elements that that previously I didn't need to think about. It was a mess, but the best I could do with the tools at hand.
If you compare this to Halogen (https://github.com/purescript-halogen/purescript-halogen/blo...) where you still have purity but can set up subscribers and listeners from any component. It's much easier to use and for some components like dialogs, it's much simpler. And this actually isn't the best example because with the latest Halogen, Portals (https://github.com/purescript-halogen/purescript-halogen/pul...) was introduced so you can launch a dialog on the spot instead of even needing to communicate between them at all.
react-solid-state
- SolidJS's truly reactive state management, in React
-
Do you think Solid is a much better version of React?
On one hand I agree with it, don't go with Solid and expect that you will 100% find a Solid job. On the other hand I think that unlike a lot of other frameworks, learning Solid could be useful even if you don't end up using it. You could even end up using Solid as a really good state management library for React https://github.com/solidjs/react-solid-state (at it's core Solid is just a state management library)
-
Solid.js feels like what I always wanted React to be
[2]: https://github.com/solidjs/react-solid-state
-
Deciding Between Solid and React for Production App
There's https://github.com/solidjs/react-solid-state for enabling Solid reactivity in React components. My plan is wire up a lot of my state management with Solid and that and then just continue using whatever React dependencies we're reliant on. If one of the Solid headless ui component libraries got mature enough, we could probably port completely then.
What are some alternatives?
solid-docs - Cumulative documentation for SolidJS and related packages.
Recoil - Recoil is an experimental state management library for React apps. It provides several capabilities that are difficult to achieve with React alone, while being compatible with the newest features of React.
solid-start - SolidStart, the Solid app framework
Performance-Analysis-JS - Map/Reduce/Filter/Find Vs For loop Vs For each Vs Lodash vs Ramda
Tiger VNC - High performance, multi-platform VNC client and server