What I would like to know here is whether the suggested serving amounts in those countries are adjusted, as well.
Sugar is bad for our health, sure, but it's not like it is rat poison. It gives easily digestible calories and in a product like baby formula, where you have defined amounts of that product to consume every day, "added sugars" in a vacuum does not seem to be such a big problem to me.
It's maltodextrin and designed to be digestible by babies. You can buy it in a fine powder marketed as "Caloreen" from Nestlé.
Our pediatrician pushed us to use it in supplement to breast-feeding because the baby was below the expected curve. For what it's worth (not much), our baby that was fed Caloreen has no sugar addiction, quite the contrary.
Knowing our pediatrician, I am 99.9% sure that he didn't have any incentive from Nestlé and was just having the baby interest in mind. I am rather blaming the weight curves that are more designed for bottle-fed babies than breast-fed ones, combined with the human tendency to focus on the indicators rather than what they represent.
Genuinely asking, is that true? Sugar or sucrose is a combination of glucose and fructose that can be broken down by water, since glucose is the basic sugar that cell uses wouldn't that be available regardless of the baby's digestive system?
Fructose is metabolized very differently from galactose. Babies also don't have a fully formed gut microbiota. Introducing carbohydrates other than lactose too early can mess that up.
Compare per 100g or per 100 calories. Suggested serving amount implies an amount that is considered appropriate to consume at one time. Which is fine for non-essential foods but nonsensical for baby formula.
BTW manufacturers can (and do) play games with the suggested serving amount to make their product appear healthier or more desirable. Standardize on a common denominator for a product category and stick to it. Then, if needed, call out how many units of the product are in that standard size.
GP's point is that you're not going to significantly reduce the suggested serving size of an essential food on account of having made it sweeter because the other nutrients are still needed.
A person's caloric and nutrient needs will vary from moment to moment, a suggested daily serving is merely an average value for average people used as an objective frame of reference.
And if we're going to argue whether a food has more or too much sugar than other foods, we need to use an objective frame of reference as a point of comparison.
Anyway, the Nestle hate in this overall thread is just as worthless as the Boeing bashing and Musk Derangement Syndrome seen in other threads.
"An objective frame of reference" sounds like it should be standardized. A suggested serving amount is pretty arbitrary and up to the manufacturer to determine, and is the opposite of "objective".
It practically is poison, it's just the effect takes years to become obvious. Obesity, type-2 diabetes accompanied by all of its implications and effects leading to miserably unhealthy lives and early deaths. I hope there is a reckoning with the industry (and the "experts" and supposed government watchdog organizations lying and feigning to protect us) someday and sugar is treated more like cigarettes with disgusting pictures of people dying on the fronts of cereal boxes.
If you have not encountered it yet, I highly recommend Ben Eater's 8-bit computer series (https://eater.net/8bit/). I don't remember any other piece of material which made me grok the deep underpinnings of CPU instructions as this. There was an almost surreal moment where my brain went "ooooooh, this is how a CPU instructions is just a complex network of switches with on/off states". Ben Eater's other material is also great, he's just a good teacher.
Building on that, the "NAND2Tetris" starts, as the name suggests, with basic logic gates and packages these low level concepts Matryoshka-style into recursive boxes with the end goal of programming a Tetris clone. See https://www.nand2tetris.org/
As someone who never enjoyed reading non-fiction books (and still doesn't), I've talked about this topic with someone who successfully devours books on the topic of "How to be a great boss". Their suggestion was that while there are many Greats, each with a devout following of their own, you as a non-convert aren't really expected to deeply study GTD and the like and then either Join The Club or better have a good reason not to like this magnum opus. That space of books can be enjoyed simply by lightly reading them, seeing what sticks with you - personally - and then moving on. Since the subject and the methods on offer are so broad, it is really ok to just think "meh" and not waste anymore time on PARA etc., if in that specific case the method just doesn't resonate with you. This is how I arrived at my very slimmed down version of Bullet Journaling - it was supposed to solve my problem and I realized that it's ok not to be a stationery influencer with forty shades of pastels arranged in slightly chaotic groups so they look nice on the Insta.
I think the corollary to this question pattern is always: "And if yes, who cares?" If the software in question is open source, the ones using it will still have enough access to it even if it were dying. The ones not using it don't want it anyway and chose one of the many other options.
More diversity amongst editors is important. Given Microsoft’s track record of EEE, one wonders what they can do with vscode. Maybe one day it will only support GitHub, maybe code sharing gets picked up and is only available on vscode, forcing you to use it because everyone else.
It’s never a good thing that Microsoft has majority market share.
Looks really interesting and I love the name! So, to deploy it in my (trusted) infrastructure, all I need is to clone it and put it on my server? I'll discuss it with my team
I found nand2tetris a very natural progression for me after finishing Ben Eater's great 8bit computer series (https://eater.net/8bit/). It just makes you grok so many basic concepts of computer design which are quite often glossed over. A perfect project to start over the holidays!
Second recommending Ben Eater. I love his videos. Two of my favorites are the introduction of loops, and the introduction of interrupts. Seeing the code he wrote re-written using these to be so much more elegant was very satisfying.
For me the 'aha' moment was the microcode section of the 8-bit computer project. Just the physical understanding of how it can take a different number of clock cycles to execute an 'instruction' - and how (in this architecture) every instruction cycle has to start with the memory address switching to the current program counter, and the data from that address being loaded into a register.
I haven't gone as far as actually building a breadboard CPU, but I was able to apply what Ben teaches to build several functional microprocessors in https://www.falstad.com/circuit/circuitjs.html, starting with basically reimplementing the breadboard model he built out.. but then after watching the 6502 series, going back and being able to see and even implement some of the things that implies about the internals of a 6502 processor.
Can someone help me understand the premise of this article? I think the goal here is to map the internal books of a business to their bank account, but I have never seen the kind of "grouping" the article seems to assume as given. In which scenarios do these groupings happen? If there are several customers, there will be different invoices and therefore separate payments. Why would the bank just throw them together, thereby creating the problem this article is trying to solve? I'm asking from Germany, in case this is one of these Europe-US kinds of differences.
If you buy something for $0.99 today, they won't bill you immediately. If you buy another $0.99 item tomorrow, you'll get a consolidated charge for $1.98. You would need to do something like this to link the $1.98 to your app/song purchases.
The reason for this is that credit card processing often costs a flat service charge + a percentage of the bill: Stripe is 30 cents + 2.9% right now. The flat portion dominates for small charges, so you'd want to combine them if at all possible. (Apple certainly gets a better rate...but also has a scale where small savings add up).
That’s how it happens, and let me add the problem occurs _between systems_.
In this example we have Apple’s charge (receipts) and the consumer’s bank withdrawals (statements). This example gives you an idea of a consumer’s purchases, which are simple to reconcile.
The post is about the Business to Business situation, which deals with greater volume and therefore more complex problems. The OP uses a toy example. If you’ve done financial reconciliation, then you will recognize the problem behind the trivial example.
Yes but you don't have access to Apple's database, and therein lies the problem. Apple might send you a receipt that itemizes these things, or it might not. If you're a business you're dealing with 1000 different Apples all of whom have different policies about how granular their receipts will be, each with a different mechanism for you to access those receipts, and each making receipts available at different times.
Meanwhile you need to do a reconciliation for your company at the end of every period (e.g. the end of every day, every week, etc.) and you don't have time to wait around for all those receipts to be collected.
Sugar is bad for our health, sure, but it's not like it is rat poison. It gives easily digestible calories and in a product like baby formula, where you have defined amounts of that product to consume every day, "added sugars" in a vacuum does not seem to be such a big problem to me.