as I said before, V8 + dynamic language + better math support = perfect environment for many applications out there
These are not fatal flaws, IMO, just gaps in need of attention.
what if your backend is nodejs? decimals for JS are mainly needed on backend
JS needs operator overloading so that it can have decimals, rationals, ndarrays, automatic differentiation, etc. Unfortunately operator overloading is a dirty word for most of the webblubs who use JS. I've given up hope of that ever changing.
Obviously, there's still significant testing to do to make sure that formerly correct code still rounds as expected, but if you're using a decimal structure like most BigDecimal ones, in memory you're already using arbitrary precision until storage anyway. Which I've done using stuff like decimal.js in JS, too, as it happens. But having it in core is the happy path for a lot of folks who don't already know that this is the way to go.
I was mostly coming at the question as “I wonder how much API overlap there is for people who already adopted libraries”.
It seems to me that with modern machines, performance is not the first priority. Floats have caused too many surprising, costly, and dangerous bugs. IMO new programming languages should really consider using safer types like decimals and ratios by default, and floats are there for those who want further optimizations.
Here are the options in .net 5:
https://docs.microsoft.com/en-us/dotnet/api/system.midpointr...
