If you read what I wrote carefully, you'll see that I said "default representation." Hardware floating-point is very useful for certain applications, and I certainly wouldn't want to give it up completely. But, more and more, it's usually not what you want.

Also, your video codec is almost certainly using parallelized fixed-point calculations, not floating-point.

Also also, are you using a pure-perl bigint implementation? That's the default.

But, more and more, it's usually not what you want.

That may be true in your world, but it certainly is not in mine.

And unilaterally declaring that the default math should be a slow, cumbersome, and very rarely actually needed, infinite precision implementation based upon your own personal requirements and other equally specious arguments, is...well, specious.

Further, it is far better that new programmers learn about the limits of machine precision early in their careers -- when what they are working on is likely to be non-critical and closely supervised -- than that they go through that early supervised period ignorant of those limitations and end up struggling to produce sufficiently performant code when it matters later.

---

With the rise and rise of 'Social' network sites: 'Computers are making people easier to use everyday'

Examine what is said, not who speaks -- Silence betokens consent -- Love the truth but pardon error.

"Science is about questioning the status quo. Questioning authority".

In the absence of evidence, opinion is indistinguishable from prejudice.