The Lessons We Learned From Moving to Recoil.js by@ksimons
1,618 reads

The Lessons We Learned From Moving to Recoil.js

tldt arrow
Read on Terminal Reader
Read this story w/o Javascript

Too Long; Didn't Read

At [Kitemaker], we recently made the leap to [Recoil.js] for our React state management needs. Kitemaker has a sync engine under the hood that is constantly syncing data in the background between clients. With `useReducer()` this always triggered a top-down re-render and we had to rely on memoization to keep things snappy. We reached for Recoil to help us minimize re-renders. We chose it over other competing frameworks like MobX because of its API and its similarity to Redux.

Companies Mentioned

Mention Thumbnail
Mention Thumbnail
featured image - The Lessons We Learned From Moving to Recoil.js
Kevin Simons HackerNoon profile picture

@ksimons

Kevin Simons

CTO @Kitemaker (https://kitemaker.co)


Receive Stories from @ksimons

react to story with heart

RELATED STORIES

L O A D I N G
. . . comments & more!