A question I recently got on YouTube: "Is recoil overkill for small apps? If so, what would you suggest otherwise?"

My answer: @recoiljs's API is very simple. So there isn't a massive set up cost to it. I think that makes it a great candidate for small projects. However...
1/ I wouldn't use it for the sake of using it. Meaning I'd start by trying to get by with just passing state using props and React context, then using something like Recoil if you need to share state between components that are far away from each other in the component tree.
2/ Also, I wouldn't use it if the shape of the data you're working with locally is near 1-to-1 with some response from an API. Use something like React Query, SWR, @apollographql, or Relay for that.
3/ Finally - it's experimental. So only use it right now if you're comfortable with using an early-stage library with potentially breaking changes across versions.

What's your take? Let me know!
You can follow @jacques_codes.
Tip: mention @twtextapp on a Twitter thread with the keyword “unroll” to get a link to it.

Latest Threads Unrolled:
Those who think consciousness raising & movement building are disconnected, or even a distraction from electoral politics have not paid attention to the history of social change.In this thread, we
Read more
The 2020s will be known as the Remote Work decadeA few predictions of what is likely to emerge[ a thread ] Third Space: Office and Working from Home will
Read more
1/29: Have you ever had a concept explained to you that helps frame complex issues you’ve been wrestling with and opens your eyes to new possibilities? A concept that I
Read more
By continuing to use the site, you are consenting to the use of cookies as explained in our Cookie Policy to improve your experience.