rpcom

That’s right - we cannot beat lack of fractions support with whatever high precision. It’s a feature that we are currently missing.

This is important suggestion that we should consider for better usability. Thanks.

We use C# “decimal” type on backend for high-precision calculations. Frankly, we do not trust third-party libraries when it comes to mission critical calculations. We would better stay safe with well-tested enterprise frameworks like .NET.

When a user converts, for example, 0.0001 millimeters to miles, most of converters out there will fail to provide the correct result due to precision loss. I know, it’s rare case, but we want to ensure that we can handle all cases without exception.

Our service uses backend to perform high-precision calculations not available through Javascript. That’s why it was an intentional decision in order to avoid any delays between entering the text and backend response. However, we might change our decision after additional performance testing.

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.

The website shares cookies with Google over Google Analytics only if cookies are accepted via consent banner, otherwise the website browsing is completely anonymous. Regarding 1496 partners, these entities will not get any information if there is no services associated with them plugged-in to our website (and there is no such in our case). They are just registered partners of Cookie Consent Provider that we use on our website.

Makes sense - to fill UI voids. Thank you for the feedback.

I appreciate your feedback, thanks!