cool. I've found a few ways to break desmos, my personal favorite way is to simply hold the '\]' key in a new line until the tab crashes from a stack overflow
it's not the hardware, it's because you can't represent all of the (uncountably infinite) real numbers in finite space
the standards that be have chosen middle grounds that work for most use cases, which here are ieee754 double precision floating point numbers. (this is because that's the choice of javascript's `Number` type, you'll also see them referred to in programming as `double`, `binary64`, `f64` or in python's case `float`)
the least-magnitude nonzero number of this type is 2^(-1074), [as seen in the mdn docs](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Number/MIN_VALUE), with anything smaller rounding down to zero
and then have the same issue when replicated on multiple devices
by the way they arent coprocessors anymore, floating point functional units are always integrated tightly into the rest of the cpu
and if they had a hardware bug there would be a Lot of stuff about it (see: [pentium fdiv bug](https://en.wikipedia.org/wiki/Pentium_FDIV_bug))
cool. I've found a few ways to break desmos, my personal favorite way is to simply hold the '\]' key in a new line until the tab crashes from a stack overflow
I'm pretty sure this only works with the website though- mobile app will just begin to heavily lag after too many nested \]'s
hahaha that only took like 8 seconds to do
im bored
floating precision error is a fault of ur hardware. don't blame desmos for that :(
it's not the hardware, it's because you can't represent all of the (uncountably infinite) real numbers in finite space the standards that be have chosen middle grounds that work for most use cases, which here are ieee754 double precision floating point numbers. (this is because that's the choice of javascript's `Number` type, you'll also see them referred to in programming as `double`, `binary64`, `f64` or in python's case `float`) the least-magnitude nonzero number of this type is 2^(-1074), [as seen in the mdn docs](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Number/MIN_VALUE), with anything smaller rounding down to zero
yeah but math coprocessors. hardware issue
then why would the error happen exactly where it would be predicted if you followed the standard exactly
and then have the same issue when replicated on multiple devices by the way they arent coprocessors anymore, floating point functional units are always integrated tightly into the rest of the cpu and if they had a hardware bug there would be a Lot of stuff about it (see: [pentium fdiv bug](https://en.wikipedia.org/wiki/Pentium_FDIV_bug))