This was more interesting than I expected. Who knew that many architectures have a flag that indicates that a float values is inexact, but that no language exp

This was more interesting than I expected. Who knew that many architectures have a flag that indicates that a float values is inexact, but that no language exposes that to programmers. Or that IEEE 754 isn't really a standard as much as it is a set of guidelines. He makes a compelling argument for why his proposal of the ubit/posit represents mathematical truthful statements, while floating point lies to you. The tradeoffs make a lot of sense. No more overflow/underflow. Better closure under arithmetical operations. “Floating point numbers are like piles of sand; every time you move them around, you lose a little sand and pick up a little dirt.” -- Brian Kernighan