bignumber.js VS jotai

If you use floating-points for currency (instead of whole-numbers like you probably should) libraries like bignumber.js help keep your code away from the binary floating-point pitfalls of IEEE-754 which manifests in the standard JavaScript number type:

This issue (well, another one in a widely used JS library) is what brought me to dig deeper into these "arbitrary precision" libraries and understand why this happens. I thought they were using rational numbers, but that's not the case. And this is what led me to think about how to solve this problem.

ERC20 has decimals fields and must be handled with digit awareness. I wanted to use only one library, but I used both ether.js's BigNumber and bignumber.js (for display purpose).

Most programming languages ( JavaScript, PHP, Go, Python, Java, C# ) have built-in support or 3rd-party libraries for handling this data type, even though the internal implementations can differ:

I'm working on a project where users will enter numbers like 9,999,999,999.99999 (up to 15 digits, up to 5 of them decimal) and we are having a problem with Numbers losing precision beyond certain number of digits (a typical issue for IEEE Standard 754 Floating Point Numbers, the 0.1 + 0.2 problem). I've solved this problem in a few projects before with the help of decimal.js or bignumber,js . In those cases, we kept user-input as strings and used a few custom-made numeric textbox widgets to accommodate this. Unfortunately, those widgets were proprietary... Now I need one again, but can't find anything. Do they exist?

Either avoid floating-point, perhaps using BigInt, or use a library like BigNumber.js. (Incidentally, I wrote an eslint plugin to enforce its use.)

To solve the problem while JavaScript waits on its own BigDecimal API, you can use something like bignumber.js to perform your calculations.

You need to use something like BigNumber.js

Daishi Kato, creator of Zustand and Jotai, says there are a few things we need to support RSC serialization:

I've just published jotai-wrapper, a super tiny and simple utility library that makes using jotai even simpler. It comes from the necessity to migrate a project with react-context-slices to jotai. Both libraries share a similar API. While in react-context-slices you have the useSlice hook, in jotai you have the useAtom, useSetAtom, and useAtomValue hooks. In react-context-slices you define either React Context or Redux slices, while in jotai you define atoms. The need for the migration from the first to the second was a high memory usage by react-context-slices when using React Context slices.

Atom-based: splits states into tiny pieces of data called atoms, which can be written to and read from using React hooks. In this group, we have Recoil and Jotai.

jotai Is the signal based state manager I recommended, offering the best developer experience (in my opinion) as it eliminates the necessity to define and update a global store

Jotai 🧙‍♂️

Atomic libs include Recoil, Jotai, and the one I maintain: Zedux. Zedux especially was designed to work well with sockets and RxJS observables and has been getting some traction recently, so of course I recommend checking it out. Feel free to hmu with any questions.

Global State Machine: Jotai (great for any state that needs to be stored globally for your application)