1/0 = 0
My problem with &quot;1&#x2F;0 = 0&quot; is that it&#x27;s essentially masking what&#x27;s almost always a bug in your program. If you have a program that&#x27;s performing divide-by-zeroes, that&#x27;s almost surely something you did not intend for. It&#x27;s a corner case that you failed to anticipate and plan for. And because you didn&#x27;t plan for it, whatever result you get for 1&#x2F;0 is almost surely a result that you wouldn&#x27;t want to have returned to the user.<p>When encountering such unanticipated corner cases, it&#x27;s almost always better to throw an error. That prevents any further data&#x2F;state corruption from happening. It prevents your user from getting back a bad result which she thinks she can trust and rely on. It highlights the problem very clearly, so that you know you have a problem, and that you have to fix it. Simply returning a 0 does the exact opposite.<p>If you&#x27;re one of the 0.1% who did anticipate all this, and correctly intended for your program to treat 1&#x2F;0 as 0, then just check for this case explicitly and make it behave the way you wanted. The authors of pony are welcome to design their language any way they want. But in this case, they are hurting their users far more than they are helping.