proposal-decimal VS eslint-plugin-big-number-rules

Bloomberg are currently sponsoring Igalia to work on adding native Decimal number support to JavaScript.

https://github.com/tc39/proposal-decimal

This is an active proposal and was last discussed in the September 2023 meeting.

would it be possible, for example, to access the standard decimal library of C# or Python via Javascript, thus not having to wait for the TC39 spec / implementation? [1]

[1] https://github.com/tc39/proposal-decimal

There's a BigDecimal TC39 proposal to bring this kind of thing to the native language, but until then you have to choose between accuracy and performance.

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

TC39 is now advancing Built-in decimal datatype in JavaScript.

given the popularity of javascript, it's about time we had better native tools for dealing with numbers in general, but it seems like the discussion is very slow on this front. for instance, the decimal proposal is still at stage 1 [1]. and no, BigInt does not solve that.

[1] https://github.com/tc39/proposal-decimal

In the future, JavaScript will hopefully get base 10 arithmetic: https://github.com/tc39/proposal-decimal

And they did bite me, so I wrote this eslint plugin to help out a FinTech app that was experiencing a number of such bugs.

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

I wrote an eslint plugin for it.

For example, say you want to avoid using native arithmetic in your finance calculations to avoid the infamous binary-floating-point problems. There's no way to get standard.js to warn you about that. But (warning: self promotion) an eslint plugin can be written to do that for you. :)