BodilessGaze

DEI stands for "DS2 Enjoyers Inclusive"

I don't think having well-defined precision is a rare requirement, it's more that most devs don't understand (and/or care) about the pitfalls of inaccuracy, because they usually aren't obvious. Also, languages like JavaScript/PHP make it hard to do things the right way. When I was working on an old PHP codebase, I ran into a popular currency library (Zend_Currency) that used floats for handling money, which I'm sure works fine up until the point the accountants call you up asking why they can't balance the books. The "right way" was to use the bcmath extension, which was a huge pain.

I work at big tech (not MS) and yes, the comp package really is that good, though not as good as it used to be. I immediately doubled my total comp when I came here from my last job, and now it's ~5x. I could retire right now if I wanted, so I don't care about layoffs anymore.

Yeah, it got really popular when the Bible dropped in the 2nd century BCE. The Noah flood story was basically a copy-and-paste of the Epic of Gilgamesh. Bible nerds were annoying af.

nah dude, there was plenty of room. I was 5,584,917,772 in line and I remember it was only about half full.

The Epic of Gilgamesh

Cuelang: https://cuelang.org/docs/reference/spec/#numeric-values

Implementation restriction: although numeric values have arbitrary precision in the language, implementations may implement them using an internal representation with limited precision. That said, every implementation must:

• Represent integer values with at least 256 bits.
• Represent floating-point values with a mantissa of at least 256 bits and a signed binary exponent of at least 16 bits.
• Give an error if unable to represent an integer value precisely.
• Give an error if unable to represent a floating-point value due to overflow.
• Round to the nearest representable value if unable to represent a floating-point value due to limits on precision. These requirements apply to the result of any expression except for builtin functions, for which an unusual loss of precision must be explicitly documented.

That works until you realize your calculations are all wrong due to floating point inaccuracies. YAML doesn't require any level of precision for floats, so different parsers on a document may give you different results.

YAML doesn't require any level of accuracy for floating point numbers, and that doc appears to have numbers large enough to run into problems for single-precision floats (maybe double too). That means different parsers could give you different results.

that's what zero sausages does to a mf

In a sense, AI is already fucking with everyone's brain when it comes to mass-produced ads and propaganda.

That describes like 99% of my showers.