Is it safe to implement Git Repos with few users, even when they're well maintained (jotai stuff)?
I'm a Dev at a company that actually respects my input on things, and I saw a wonderful opportunity to implement Jotai. It was the perfect use case for it, and when I implemented it, every other Dev loved it (we were doing "state prop drilling" trough components, so to speak, and it was really annoying).
However, my Dev Lead (whom I respect immensely) got worried about Jotai, since he never heard of it.
We had a brief discussion about the git repository and his insecurities.
He pointed out that the amount of users of Jotai is very small when compared to the amount of users that use Redux, for example (source: https://npmtrends.com/jotai-vs-react-redux-vs-recoil-vs-zustand).
In the end, I convinced him that Jotai is "the hot new thing", that he simply didn't hear about because his focus left development for a while, and that if we follow his logic, no repo will ever get used.
We managed to reach a compromise where we still use the repo, but we freeze the version, for fear that a future update would break stuff, since there "aren't that many users, even though its well maintained".
Ever since I've been feeling a bit insecure about the whole ordeal... is it a good idea do implement a repo with few users, even if it is well maintained? Is the answer different depending on the scope of the project (since the product I'm developing is pretty big, and important for the clients)? Is freezing the version of the repo a good compromise, or does it make things worse?
jotai vs react-redux vs recoil | npm trends
Comparing trends for jotai 1.8.4 which has 183,945 weekly downloads and 10,111 GitHub stars vs. react-redux 8.0.2 which has 6,254,251 weekly downloads and 22,376 GitHub stars vs. recoil 0.7.5 which has 320,505 weekly downloads and 17,671 GitHub stars.
5 Replies
Unknown User•3y ago
Message Not Public
Sign In & Join Server To View
Isn't freezing the version standard practice anyways?
Honestly have no ideia... I just run updates on my npm packages every so often. Is it not a good practice?
Fair enough
Well, if you know for sure there are no breaking changes it's fine.
But a project I'm currently working on has a ton of dependencies and we've had issues with breaking changes in the past
Gotcha! Will keep in mind! Thanks!