Congrats, you figured out the worst possible title for the post.

I took thermodynamics as an elective, without realizing that was the weed out class for mechanical engineering majors. Biggest mistake of my life.

Google is alleging the first known version is 7 years old, which would predate AI - but I cannot open the link it only takes me to the community homepage.

There were definitely AI models for restoring images 7 years ago. I remember using https://github.com/jantic/DeOldify (which started in 2018) about 6 years ago to colorize an old photo album, and it worked well.

yep, it’s wood

What about the M-expression version (f[x])?

I’m partial to Terra’s theme, but yeah, that whole OST is amazing.

Where are the Snowdens of yesteryear?

And it’s highly effective!

Predation accounts for a relatively low rate of nest failure: only 34% compared to an average of 80% for birds in similar habitats. This may be enabled by their well camouflaged nests, or simply the lack of local predators.

https://en.m.wikipedia.org/wiki/White-browed_tit-warbler

Only for male fashion. For the ladies, brown is in.

You’re going to regret those words when you die and face judgment before the Moth God.

Is it really worth it?

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.

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.

Bad news: this article was retracted for fraud after the journal discovered the author wasn’t actually a dog.

Depends on the monkey

Image is accurate, since without bugs, the food chain collapses and takes society with it, and the survivors will have to migrate to rural areas that can support a hunter-gatherer lifrstyle.

Do you have a justified true belief they aren’t the same fig?

It’s a parody of https://en.m.wikipedia.org/wiki/The_Scorpion_and_the_Frog