Hacker News Reader

They didn't write a whole new calculator engine, just a new UI and app wrapper for the old one.

If the new one just wraps the old one, but the new one breaks on certain inputs, how is it breaking? Maybe the outer "new" layer uses a new string to number parser than the inner "old" layer used to use, and that's where the bugs are being introduced?

They continued to update the underlying engine with new features and bug fixes and new bugs, they just didn't rewrite it from scratch.

Apparently a recent update also fixed a longstanding problem where the square root of a perfect square integer doesn't give you the exact right answer, so maybe there was a general change to the implementation of exponents and roots which may have introduced this bug too.

Reply on news.ycombinator.com