Get used to seeing this kind of cheap shots and half-ass projects everywhere. With AI, going from idea to half-ass now cost only 150$ per month and near zero skills.
Not my area of expertise, but my understanding is that this is an extremely limited claim (i.e. unborn babies / neonatal supplementation, or children with genetic defects), and not something you can even remotely generalize to "children" as a whole. The way we teach this in biochem 101 is "arginine is conditionally essential", with the "conditional" being "periods of stress or sickness".
In any case, I seriously doubt the author is talking about this, given the imprecision of the language. Also, eating this wheat specifically for arginine supplementation is goofy gym-science. Arginine is trivial to supplement.
More like: we all need arginine, but our body makes it, so we don't need to supplement it. Wikipedia writes this:
Preterm infants are unable to synthesize arginine internally, making the amino acid nutritionally essential for them. Most healthy people do not need to supplement with arginine because it is a component of all protein-containing foods and can be synthesized in the body from glutamine via citrulline.
i don't think LoC is the metric. sometimes fewer lines of code results in a larger attack surface through type coercion / widening, poor abstractions, hiding or stuffing behavior (modules that do everything), etc. to me, making code easy to understand, test, fuzz, and verify is more important. sometimes that requires more lines of code.
LoC *IS* the metric. It is obviously not perfect tho but still the best one to compare software surface. Including to compare the same solution in different languages and platforms. The less code you need to manage, the less code you need to change and the less code you need to hold in your head to understand it (or in the LLM context nowadays).
More abstract code probably results in more high-abstraction-level bugs per LoC, but also less low-abstraction-level bugs so I'd guess it about cancels out to an even rate per LoC.
A single line in C++, Rust or Haskell can have a really subtle logic error. A single line in assembly can't, but it has that same likelihood of having a register allocation error instead, and when you add up all the many lines of assembly you probably still wrote the same number of logic errors as the C++ version.
in a utopian future, addictions like that would be cured and siloed. hopefully, those with motivation to understand the mechanisms of human suffering would be in charge of policy.
many common nginx setups and hardening suggestions would make it very difficult to exploit. as well as any sort of distributed architecture that doesn't pin requests to clients.
there could be other undiscovered paths to exploit this vulnerability though. the PoC here uses the disclosed path for exploiting on patch day, minus mod_php.
reply