We use high-precision calculations up to 28 decimal digits that cannot be provided by numeric types available in Javascript. That’s why we do our calculations on the backend.
As others noted though, thats a lot of precision that maybe not everyone needs, maybe a checkbox for more precision that then calls the backend?
Why could you not have used one of the bigfloat[1] JavaScript libraries that exists? Is there an operation the service requires which is not supported by them?
In any case, thank you for the free service. I'm sure this will be useful to a lot of people. While I would not use a cloud-based calculator, I'm sure a lot of laypeople don't care how it's done, and I appreciate your focus on utmost accuracy.
Although I was a little, um, assertive in some of my comments here, I honestly mean them constructively, in the spirit of "here are some things you might consider to make it more useful". I apologize for missing the joke.
Please don't be the calculator that ignores significant digits and encourages people to write nonsense things like "an adult blue whale can be up to 29.9 meters (1177.16535 inches) long".
Pretty sure there aint one.
https://en.wikipedia.org/wiki/List_of_physical_constants
https://physics.stackexchange.com/questions/497087/what-is-t...
> Think about that. We have a circle more than 94 billion miles (more than 150 billion kilometers) around, and our calculation of that distance would be off by no more than the width of your little finger.
Anyone who needs more precision than that is almost certainly sitting next to a computer with bespoke software running on it.
Also, for ux reasons, I'd love this as a browser extension. Cloudy Calculator can do a lot of it but was recently deprecated as a result of the Manifest v2->v3 requirement from Google.
You can't give exact answers without representing everything as fractions, even for the easy ones like mm to miles. With that being true, anything more than JavaScript's own precision is probably unhelpful.
The kind of person solving problems where they'd need to convert between miles and mm would rewrite the constant as "1mi = 1,609,344mm". No one in the real world is adding up 0.0001mm intervals until they get to a mile, so you're solving for a problem that doesn't actually exist.