Pretty neat. I adapted the state management of hooks to Haskell a few years ago. Could be used for similar purposes, but there's no support for templating or styling yet: https://github.com/benweitzman/hooks
The gist of the argument is that addition + other operations on non-computable numbers (which the real numbers contain) require infinite algorithms or something similar (unlike addition on computable irrational numbers which may require infinite work, but the algorithms are finite). You can therefore get situations where, say, the tenths digit in a sum of non-computable numbers is not defined because of potentially infinite carries, and there's no way to determine if the sequence of carries terminates or not. He discusses the problem in the context of different representations of real numbers, including infinite decimals, cauchy sequences, and dedekind cuts etc. This is just the gist of it.
Applying the incompleteness theorem wouldn't say that every piece of complex code has unpredictable outcomes, but that there exists some pieces of code that have unpredictable outcome.
Seems like in this case the outcomes were entirely predicted by the "attacker".
The meat industry is also cost effective due to massive government subsidies, at least in the US. Would these subsidies be available to lab grown meat operations?
How are you comparing nutritional value between meat and plant products? There are literally hundreds of millions (if not billions) of people that have been eating vegetarian diets for their entire lives, and these types of diets have been popular for millennia.
Strict by default is becoming increasingly popular in production. It makes programs behave a lot more predictably for many common use cases. Extensions are enabled on a module by module basis so if you turn on strictness by default, you can still opt in to laziness if you have certain data structures/algorithms that rely on it.
I've used Haskell + Servant help reduce backwards compatibility issues with an iOS app depending on the API. We had Servant automatically generate OpenAPI specs from the API, and then diff them against the version in prod during CI testing.
Certainly possible with other languages + frameworks, but I felt really confident relying on it to catch issues due to the strong type guarantees.
I made a vegan pavlova just the other week. Took chickpea juice straight out of a regular can of chickpeas and whipped it up with sugar. No adjustment necessary.
The logic is not "if people buy it, it must be good", but more "if people buy it, there must not be something else that they can buy that gets them what they want for less".
I like using the layering with my Ergodox keyboard because it helps keep special characters I frequently use (parens, braces, brackets, etc) right under my fingers in a relaxes position. It alleviated a lot of finger strain I was feeling reaching for the keys (and reaching for shift especially) so frequently.
Though I do have a standard layout with the number/symbols row available as well.
I've paid candidates and been paid by potential employers to complete take homes. I've also given candidates the opportunity to substitute a piece of open source code in place.
This is admittedly still biased towards people who have available time, paid or unpaid, but I think it's a step in the right direction.