The product that this article is advertising seems to be pretty inaccurate and their marketing seems to be burying that information.
The big copy on the front page says:
> Your Apple Watch *tracks* VO2 Max—one...
While you have to read through FAQ where you see:
> The watch *estimates* your cardio fitness during outdoor activities and stores it in Apple Health, which our app reads automatically.
All emphasis are mine.
I think it's a little disingenuous to sell this as "Your VO2 Max, finally visible" when it's actually just an estimate from a watch, based on biomarkers. When the real VO2 is measured in a lab with a more involved equipment.
A 2025 validation study involving 30 participants found that Apple Watch underestimated VO2 max by a mean of 6.07 mL/kg/min (95% CI 3.77–8.38) when compared to indirect calorimetry, the gold standard method. The mean absolute percentage error (MAPE) was 13.31%, and the limits of agreement showed considerable variability ranging from -6.11 to 18.26 mL/kg/min [1]. Another 2024 study found similar results, with the Apple Watch Series 7 showing a MAPE of 15.79% and poor reliability (ICC = 0.47) [2].
There's (vo2master) device that can apparently measure it in one breath; there was a video on some swimmer using it on turnaround without much interference with their exercise. $7k though.
I've also been interested for some time in how metabolism works and wanted to debunk the popular myth for my friends that exercise burns a lot of calories, since I was under the impression that around 80% of energy we burn is just by "living" - breathing and thinking.
Reading this article I'm a little confused by the author's conflation of brain energy and the energy expenditure of the body as a whole. In the beginning they mention:
> "Your brain consumes roughly 20 to 25% of your body's total energy at rest"
while later they say:
> "Even chess grandmasters, who sit for hours in states of intense concentration, burn only about 1.67 calories per minute while playing, compared to 1.53 calories per minute at rest"
That second figure seems to refer to whole-body expenditure, not just the brain. And intense cognitive work doesn't happen in a metabolic vacuum - there's increased cerebral blood flow, elevated sympathetic nervous system activity, changes in heart rate variability, hormonal shifts (cortisol, adrenaline). These all have systemic metabolic costs that go beyond the glucose the neurons themselves consume. So the "it's just a banana and a half" framing might be undercounting by quietly switching between brain-only and whole-body measurements.
Also somewhat related - the link to businessinsider about chess grandmasters is broken, but another very interesting rabbit hole here is how energy expenditure is actually measured. A lot of what consumer devices and even many studies report is based on proxy biomarkers like heart rate, HRV, weight, age, and sex, run through linear regression models. True calorimetry (indirect via gas exchange, or direct in a metabolic chamber) is expensive and impractical outside lab settings. That means the precise calorie figures cited with such confidence - the "100 to 200 extra calories" from a day of thinking, or the per-minute burn rates of chess grandmasters - likely carry wider error bars than the article suggests. We don't really have a great way to measure real-world energy expenditure accurately at the individual level, which makes me a bit cautious about the neat narrative of "thinking is calorically cheap, full stop."
That said, the core point about adenosine accumulation and perceived exertion affecting training quality is fascinating and well-supported — that part of the article is genuinely useful regardless of the calorie accounting.
> Can you expand on that please? Because I can tell you as a matter of fact that when I go for a run for an hour I burn well over 800 calories
Sure - how did you arrive at the 800 kcal figure? Most likely a wearable or an app, and those estimates are based on rough linear regressions from weight, age, sex, and heart rate - not actual calorimetry. The error margins on those numbers are significant, but the devices present them with false precision that makes people treat them as ground truth.
Even setting accuracy aside, the framing is the issue. Your basal metabolic rate - just keeping your organs running, blood circulating, cells maintained - accounts for 60-70% of your total daily energy expenditure. Add the thermic effect of food (~10%) and you're at roughly 70-80% of your energy budget spent before you even lace up your shoes [1]. Exercise typically makes up the remaining 20-30%. So that hour of running, while genuinely beneficial for a hundred other reasons, is a relatively small slice of your total daily burn. And not all calories are equal on the intake side either - your body spends 20-30% of the energy in protein just to digest it, compared to 0-5% for fat, so "800 kcal burned = 800 kcal of anything eaten" doesn't hold up.
That's what I mean by "myth" - not that exercise burns zero calories, but that the popular mental model of "I ran for an hour so I earned X calories of food" is built on inaccurate measurements, treats all calories as interchangeable, and overweights exercise relative to what your body spends just existing. Curious though - do you track your intake with the same rigour, and if so, do you find the numbers actually add up in practice?
> That's what I mean by "myth" - not that exercise burns zero calories, but that the popular mental model of "I ran for an hour so I earned X calories of food" is built on inaccurate measurements
Over the last few of decades there's been a lot of lab research calculating the gross efficiency of the human body with different factors (size, sex, fitness etc) and I think these estimates that sports apps give are very close.
If you cycle with with something that can measure power output you can calculate the mechanical work done by the body exactly during that exercise period and convert to energy "burnt" (1 watt/hour = 3.6 kJ = ~0.86 kcal). 220 Watts for an hour (I couldn't do that but a good cyclist can) is about 800 calories.
To the degree the body diverts any housekeeping or thermogenic calories to exercise calories, which from basic biological adaptivity and thermogenic control must be true at some level, that math will be misleading.
Not that doing x work doesn’t burn y energy, but that +x work in exercise does not burn +y energy at the end of the day.
Exercise is an alternate heat source, approximately 1-to-1 with thermogenic heat (albeit, not distributed as evenly). So much so that our body has to switch to cooling strategies.
And the body can respond to exercise expenditures by reducing other expenditures and using calories more parsimoniously in other dimensions.
It is interesting that during periods in which I have a habit of daily low intensity exercise, I feel like I have more energy than periods I don’t do any exercise, even if my calorie intake is the same.
Another noticeable effect is any allergies from local plant life I get clear up quickly during and after exercise. My immune system runs a tighter, less reactive ship.
Those baseline calories are not just often underestimated in a static sense, but are also dynamically adaptable.
One reason may be is that we evolved to burn far more overt calories through a day than our extra-exercise day burns. Our body has mechanisms for storing surpluses but almost certainly raises baseline use as well. Which is easily diverted back to exercise.
On the other hand, beyond any net expenditure from regular lifting weights (as work), to the degree greater muscle mass is achieved and maintained, weight lifting directly raises the body’s baseline expenditures.
>It is interesting that during periods in which I have a habit of daily low intensity exercise, I feel like I have more energy than periods I don’t do any exercise, even if my calorie intake is the same.
In the same vein as much of the rest of what you're saying, the other thing that I feel like people always neglect with their "Calories in/calories out" and "Bodies can't violate thermodynamics" is that the human body can adjust how efficiently it processes food, colloquially known as a "slow" or "fast" metabolism.
While it's true that the human body has no answer to a true calorie deficit (except the incredibly powerful and effective one of tweaking satiety and hunger signals), as long as you're eating more calories than you're strictly burning, your body can simply take longer or less time to digest the food you put into it and extract more or less energy from what you're eating, which can make an enormous difference without you changing your intake at all. Which means that people can absolutely eat identically, have identical appetite levels, and have extremely different body types.
If you're exercising more, sure, your body will make you more hungry, but it will also work harder to squeeze every possible calorie out of what you're already eating. If you cut down on what you eat, your body will work even harder at it, to the point that you could literally eat less, work out more, feel hungry and tired all the time, while getting fatter, because your body is worried that you're in a famine and in a physically stressful environment and is desperately trying to signal to you to conserve as much energy as possible, eat as much as possible when you find food, and at the same time trying its best to make the most of the food you give it.
And at the same time, someone else's body might simply not do that. It's crazy!
I tracked intake, calories burned(from Apple watch with activity tracking turned on for any specific exercise) and weight for 12 weeks as part of 75 hard and found my daily weight decreases were exactly in line with what you'd expect given the estimated deficit 95% of days and 100% at the weekly level.
I don't track consistently anymore only when I'm working towards a goal but when I have more than 2 weeks data these days it seems pretty spot on to the point I can calculate the tracked captors to target to get the desired rate of change in weight pretty consistently.
Thanks for fleshing out your comment. Because initially it did kind of suggest to me you were saying it burns no calories or makes _little_ difference.
I agree with all you posted.
> Curious though - do you track your intake with the same rigour, and if so, do you find the numbers actually add up in practice?
To return the courtesy, for the purposes of discussion I picked a rough estimate and rounded down significantly the actual amount I typically run. More often it's 1.5 hours a run and supposedly >1000 calories given my weight, heart rate, terrain, and speed. I also assumed the calculations are way overestimating my actual calories spent so just went for something somewhat plausible for the sake of a HN comment. As you noted calories aren't accurately reported by devices. I do not pay attention to it in massive detail either. But in practice since I run an average of about 25km a week but can vary from 0 for some weeks to 50 for others and I keep relatively good eye on my diet I notice significant changes in weight over time that tallies with effort. Three months of below that 20ishk a week and I will put on 2-3kg. The next three months I increase to 35ish+ a week and it drops off again. Would I swear to it in a court of law that I'm not miscounting meals? No way. But I feel reasonably comfortable that this is an accurate description.
You are being idiotic.
One hour of running is almost half of my minimum energy expenditure.
All the other movements in a typical day only account for about half that, unless I make sure to walk a lot more than most people would.
The brain does increase energy expenditure with activity, but as said in the article, it's quite minimal.
I have been tracking caloric input very precisely and energy expenditure with an Apple Watch (one of the most precise trackers) for a while, and I can guarantee you it all adds up.
In fact, once everything is calibrated, I could predict my weight loss/gain with a 5-10% margin of error at worst (mostly due to imprecision in food calorie accounting and inaccurate energy expenditure tracking).
Too many people try to mystify something that is extremely simple. There are some things to care about (like not going too low on the protein), but it really is all about getting the same amount of energy that you are spending, and that's pretty much all there is to it.
I think OP may be referring to the idea that the total number of calories burned in a day doesn't meaningfully change under a workout regime. Working out does burn calories, but after a few session your body starts to compensate by burning less calories in other areas (e.g. immune and reproductive system). The net result is close to zero, except in very demanding workout regimes.
I don't have the background to fully evaluate how true that is. I read "Burn" by Herman Pontzer, which at least makes a very good case for it.
I seems like it's only part of the story. If you increase exercise but also increase calorific input to match then you won't lose weight. But, the laws of energy conservation being what they are, I don't think anyone disputes that if you very significantly increase exercise but also maintain calorific input then you will lose weight as the energy must come from somewhere and there are only so many optimisations your body can make. You could of course maintain exercise levels and reduce calorific input for a similar effect, ignoring health benefits of exercise. Take an extreme case, Michael Phelps. He used to eat 12,000 cal a day because of the hours he spent swimming. Certainly not a small guy but pretty lean! So I'm totally prepared to accept there are bounds to all these statements but I still think I couldn't finish an 800 cal sandwich for lunch hehehe.
By the way, I feel the Wikipedia page there uses a lot of words suggesting that the paradox isn't at all fully understood and that there could be compensating mechanisms we aren't aware of. But I'm not in a position to dig deeper.
> I don't think anyone disputes that if you very significantly increase exercise but also maintain calorific input then you will lose weight
This is exactly what is disputed by the link you posted. They measured directly the energy expenditure (the number of calories burned by respiration) in a high-activity hunter-gatherer tribe, and in relatively low-activity industrialized societies, and found they were almost the same. So the number of calories the people consumed was not measured or relevant (and must also have been roughly the same if neither group was actively gaining weight).
Not quite, imho. The language used here is subtle and I could be clearer myself. It talks about the paradox that suggests the work _appears_ to come from nowhere, which we should all agree is impossible, thus a paradox, not that it does actually come from nowhere. Just that we don't know exactly where. The page doesn't offer an explanation for the appearance of the paradox.
For me the line "The studies suggest that controlling caloric intake may be more necessary for managing weight than exercise alone." is a possible conclusion for the apparent paradox. Note the words "may" and "alone" which indicate uncertainty. I deliberately used the phrase "very significantly" to suggest we would probably all agree that there is some bound on observing the paradox which is why I used Phelps as an example. To repeat and be clear, I think the paradox as described on the page does not say that with a very significant increase in energy expenditure there will be no weight loss with a constant calorific intake.
I guess when you say "work" you mean precisely mechanical work. If so, I don't think it is implied anywhere that the work "comes from nowhere". If a person is doing mechanical work then that work must come from respiration, ultimately. There is nowhere else for it to come from. If a person does 2000 calories of mechanical work and consumes 2000 calories of energy then there is nothing left over for anything else, and they would lose weight one way or another. But this is much more extreme than what was observed, or what happens when a person ordinarily does exercise.
The "Energy paradox" is not a logical paradox at all. It is just a confusing fact. The observed fact was that two different groups with apparently very different activity levels respire almost exactly the same amount. In other words, that an increased, but not necessarily extreme, level of mechanical work does not appear to correlate with an increased level of calorie burn. Not just that the relationship is non-linear, that the relationship does not seem to exist at all (at the measured level of exercise).
I was very careful with my words this time, hopefully there is no more misunderstanding. I think we still disagree unless by "very significantly increase exercise" you mean something like running multiple hours per day every day.
And also that the calorimetry from wearables is highly flawed and it seems to that we don't have super accurate data and what sort of activities burn the most energy.
I am also a big opponent of folks that start equating the "my wearable shows that i burned 300 kcal with that activity so it zero outs that sweet thing I ate earlier that was also 300 kcal" which is wrong on so many reasons but with a lot of workout apps and devices pushing the (inaccurate) kcal count front and center becomes more and more a of a thing.
I think it sort of depends on how you look at it. If 800 is an hour of running - that's probably "a lot" for quite a few people. But 800 is also just a sandwich. Which isn't all that much.
So if you view this from a time use perspective, just skipping that sandwich is way better than running for an hour. And many people can't spare an hour a day just to make up for a sandwich. Hence - "not a lot" - Its too expensive time-wise for the caloric balance effect it provides. Just skip the sandwich instead.
I'm talking about what happens in reality, not what the "serving size" is. Gobs of folks order a footlong at Subway and eat it for their meal.
As for nitpicking on calories: the Subway site is incredibly tough to navigate. Just use https://subwaymenupedia.com/, since averaging across location is really tough.
I wish my point were uncontroversial: millions of people buy footlongs that are over 1000 calories as a regular habit. I'm critiquing folks that are incredulous about this. Subway is just an example, you can also look at Quizno's (back in the day) and Jersey Mike's (the modern equivalent). Even my local deli serves sandwiches well beyond 800 calories as their special. It's not an interesting argument to have, though. Shops wouldn't offer these meals if folks weren't buying, and I don't believe everyone's doing take-out with the second half for dinner or lunch the next day.
You're really arguing about whether that 800 calorie run could be offset completely by a normal meal. I think it's fair to say that runners doing 800 calorie runs aren't going to Panda Express, but also at the same time:
I agree with the general message, but I'm curious what ingredients go in your 800 calorie sandwich. That's more than a double Big Mac with 4 patties (780 kcal)!
You need to eat roughly somewhere between 1300 and 2000 Cal every day to maintain your weight even if you are doing to exercise at all.
If you want to lose weight, it's far easier to remove 800 Cal from your diet, at least time wise, then it is to exercise 800 Cal's worth every day.
Either way, if you're losing weight at any appreciable rate, you will feel hungry (at least if it's not chemically induced in some way, such as chemo or GLP-1 inhibitors or similar). That's just something you have to get used to if you want to lose weight.
This is well-intentioned but I think it oversimplifies in ways that can actually be harmful. "Just get used to being hungry" is rough advice to give people - chronic hunger is one of the main reasons diets fail, and framing weight loss as a willpower contest against hunger ignores that satiety is heavily influenced by _what_ you eat, not just how much. A 400 kcal meal of protein, fat, and fiber will keep you full for hours; 400 kcal of simple carbs will leave you hungry again in 45 minutes, in part because of the insulin and blood glucose dynamics involved.
The calories in/out model isn't wrong exactly, but it's so reductionist that it becomes misleading in practice. It omits hormonal responses (insulin, leptin, ghrelin), the thermic effect differences between macronutrients (your body burns 20-30% of protein calories just processing them vs 0-5% for fat), gut microbiome composition, sleep quality, stress hormones, meal timing, and individual metabolic variation. Two people eating identical calorie counts can have very different outcomes. Telling someone "just eat less and accept the hunger" without any of that context can set them up for a miserable yo-yo cycle - or worse, a disordered relationship with food.
No, the common "wisdom" you are puppeting here is harmful because it just doesn't work.
We have been telling people for decades now to be worried that they might harm themselves by too much restriction and it is just wrong. What is harmful is being over weight. What is harmful is then confusing people that they are somehow going to lose weight without much restriction or being hungry.
This also scales really bad with age because as you age the CNS recovery gets worse and worse compared to muscle recovery.
At 55, there is simply no way for me to lose weight other than being hungry. It is impossible to recover from the amount of exercise that would be needed. The reality is that no one needs to worry about too much restriction until they are down to around 12% or so body fat. The fact a person's bodyfat % is never mentioned in this is exemplary of how bad the standard advise is.
Most people have too much leptin and leptin resistance. Then those same people get the same bad advise over and over to not restrict too much because you don't want to be like an anorexic or extreme athlete and have too low of leptin. Of course, ignoring that the anorexic and extreme athlete are going to have incredibly low bodyfat percentages.
I think the advice that everyone who is overweight or obese really needs is to experiment with different ways of reducing their food consumption while managing their hunger and cravings, and find out a method that works for them. I don't think there's any universal solution. Even saying "eat less simple carbs, those make you more hungry because of this and that chemical pathway" is not good universal advice, because food consumption is not strictly tied to hunger in all people. It is up to you as the one who wants to lose weight to experiment and figure out what motivates you and works for you longer term.
For example, I don't feel satisfied with my meal if I don't feel slightly full. So, what has worked for me is to generally have a single large meal per day, in which I will typically eat whatever I've been really craving since my last meal. In some days that might be steak and brocolli, in other days it might be a McDonald's meal, or some cake. When I get cravings, it's far easier for me to defer them to tomorrow's meal than it would be to just stop eating junk food entirely, or to eat half a burger and two fries from the bag. The exact opposite might be true for other people, and you won't really know until you've tried for yourself.
One thing I will note - I think one of the concerns of the poster you are replying to with focusing too much on enduring hunger is that it might lead some people to develop anorexia, which is indeed a huge problem, even when the person is really overweight (since their anorexia will not just go away once they've lost that extra weight, it will keep going until they get dangerously malnourished).
I don't think I implied that the only thing that matters to weight loss is CICO, and that you only need willpower to lose weight. I don't personally believe this at all.
My point was instead that whatever effort you can spend on weight loss is better spent on managing your diet than increasing your level of activity (though I should also say that fitness is important beyond weight loss). Even when I said you can reduce 800 Cal of food, that doesn't mean "just skip a meal" (though that is also a valid strategy for some people). It can also mean "eat different kinds of food".
However, I do strongly believe that for any weight loss at a significant pace (say, 1kg/month or faster), and assuming it's not just a correction after a short stint of overeating (as in, it's more than losing 1-2kg you put on over Christmas) - then some feeling of hunger is inevitable. Losing long-term accumulated weight is going against your body's "wishes" (especially in the lipostat model, where your body has a set fat% equilibrium that it seeks to maintain), and hunger is an inevitable response to that. How much hunger you will feel can be controlled by better food choices and so on, but you will have to also get used to feeling some level of hunger.
For cardio sure but for weight training you're burning calories and tearing muscle fibres to increase size/strength. Also depending on the running you're doing, you're likely staying fitter.
Sure it's easier to fast but you're missing out on the other benefits associated with exercise.
> Sure it's easier to fast but you're missing out on the other benefits associated with exercise.
This is very true, exercise is very important for health regardless of its effect on weight.
> For cardio sure but for weight training you're burning calories and tearing muscle fibres to increase size/strength.
True, but you need to spend even more time to rack up 800 Cal worth of exercise by weight training compared to doing cardio, as a beginner or even an intermediate level gym goer.
It is also true though that weight training, if you actually successfully build muscle mass, can significantly increase your BMR and thus help with losing weight in that way, even if you're not spending hours or lifting hundreds of kilos at every session.
Yeah, unfortunately back of envelope physics math about the kC burned for lifting weights is deeply disappointing. Luckily our bodies are quite inefficient compared to a bomb-calorimeter, because back of envelope gets me less than a (k)calorie per 3 sets of 5 lifts, if you just do lazy potential energy math.
A tiny technical note - Cal is the official symbol for a "large calorie", equal to a kcal, 1000 cal, if you want to be precise but concise on the exact type of calorie you're talking about.
Not running, but in cycling we have power meters, and some workouts (eg 2 x 20' threshold) will definitely burn in the range of 800 calories in an hour. The energy measured by the power meter for this workout is 800 kJ for me (my threshold being around 260W). Now it turns out the conversion factor from kJ to calories is 1/4, but the body is only 25% efficient when producing calories for cycling, meaning one has to burn 4x the amount measured by the power meter. So that's 800 calories for this kind of workout, for me. I wouldn't be surprised if runners of similar fitness doing similar workouts had the same energy expenditure.
> debunk the popular myth for my friends that exercise burns a lot of calories
Depends on your level of exercise. I often cycle 100km per day and can tell you if I ate only the 2000 kcal I hypothetically need I would go into a strong deficit.
There's been metabolic studies that show that this isn't true. Comparisons of total caloric usage of completely sedentary people and people who have high exercise load are indistinguishable. There is a large difference among individuals, but not correlated to exercise levels. Sedentary people who start training hard will have a spike in caloric usage for a few months, but their body adapts and calorie burn returns to the same level that it was when they were sedentary. This was new research, so there wasn't an explanation for it. The authors hypothesized that it could be that the body reduces caloric spend on other things, like stress responses, when it is adapted to high exercise levels/ They did note that some extremely elite athletes can temporarily increase their caloric burn (think Michael Phelps eating 10k calories per at some points when training for the Olympics) but its not something most people can achieve or sustain.
Absolute nonsense. The claim is that if I produce 2.5watts per kg in body weight for 2 hours, I’m not going to burn any extra calories? So when I “bonk” and exhaust glycogen stores due to underfueling that’s actually not true?
I think that the claim is that what you're experiencing absolutely does happen, and your body responds by cutting corners on your baseline when you're sleeping or sitting around on the couch to avoid you starving to death (because it doesn't know that you can trivially increase your food intake if needs must).
> if I ate only the 2000 kcal I hypothetically need I would go into a strong deficit
Right, and that's kind of my point - the "2000 kcal" figure is itself part of the problem. It's a rough global average that doesn't account for your sex, age, weight, body composition, activity level, or even climate. It's a number on a food label, not a physiological reality for any specific person.
And even if you could nail down your actual total daily energy expenditure, calorie counting treats all calories as equal, which they aren't. Your body spends 20-30% of the energy in protein just to digest and metabolize it, compared to 5-10% for carbohydrates and 0-5% for fat. So 100 kcal of chicken breast and 100 kcal of butter are not metabolically equivalent - your body nets significantly less usable energy from the protein. This is the thermic effect of food, and it alone accounts for roughly 10% of your total daily energy expenditure.
Speaking of which - basal metabolic rate (just keeping your organs running, blood circulating, cells maintained) accounts for about 60-70% of total daily energy expenditure. Add the thermic effect of food on top and you're at roughly 70-80% of your energy budget spent before you even stand up from bed [1]. Physical activity - including your 100km rides - typically makes up the remaining 20-30%, though obviously that range is wide and shifts dramatically for endurance athletes.
So yes, of course people who cycle 100km need more fuel. Nobody is disputing that. My point is that most people vastly overestimate how many calories exercise burns relative to what their body spends just existing, and they use kcal as a universal unit of nutritional value when the body's actual energy extraction varies significantly by macronutrient composition. People optimizing purely on calorie numbers are working with a model that's far rougher than they think.
And this whole picture gets worse with wearables pushing calorie counts front and center. You see it all the time - "my wearable shows that i burned 300 kcal with that activity so it zero outs that sweet thing I ate earlier that was also 300 kcal" That's wrong on multiple levels - the device estimate is inaccurate to begin with, the thermic processing of that pastry isn't equivalent to the "300 kcal" on its label, and your body doesn't do neat arithmetic like that anyway. But with every fitness app and smartwatch plastering a big kcal number on your workout summary, it's becoming the default way people think about food and exercise, and it's reinforcing exactly the wrong mental model.
That specific aspect might end up irrelevant for dieting, which is exciting since it flies in the face of intuition. It seems that when it comes to long-term modes of existence (as opposed to, say, the one day of the marathon) the "activity level" doesn't really affect how much energy your body uses.
> In this study, we used the doubly-labeled water method to measure total daily energy expenditure (kCal/day) in Hadza hunter-gatherers to test whether foragers expend more energy each day than their Western counterparts. As expected, physical activity level, PAL, was greater among Hadza foragers than among Westerners. Nonetheless, average daily energy expenditure of traditional Hadza foragers was no different than that of Westerners after controlling for body size.
Thank you for your comment. I didn't know about protein and carbs and fat calories not being metabolically equal. I'm hoping that calories counting apps would account that in, but I know that it's probably not the case
TypeScript never promised improving safety, maybe it’s a common misconception. But TypeScript has no runtime mode or information. You were always at the mercy of running and not ignoring the typechecker. Nothing stopped you from running ts-node or tsx on code with egregious type errors. TypeScript is more like a linter in that regard.
I think it's not fair to say that Typescript isn't about improving safety, just that the mechanism isn't the same as with other languages. Typescript had always allowed you to ignore the type checker (in fact, the default configuration will always attempt to emit compiled Javascript, even if the source Typescript has type errors). But if you run the type checker on every commit (via e.g. CI or a precommit hook), then you can be sure that the code you release is correctly typed, which will not guarantee it is safe, but makes it more likely.
I agree that it's better to think of Typescript as a linter that needs specialised annotations to work, rather than a type system like you might find in Java or Rust.
What, pray tell, would be the point of putting all that type information in there, and then have it checked (via tsc), if not for the sake of safety? What other use would this have in your opinion?
No, I don't think there really is. But to be execute is even more clear that it's just... executing the code, whereas I could maybe understand someone being confused that run implied some level of type checking.
This is misleading. It is not transpiling TS in JS, it is transpiling a subset of TS into JS. If my normal TS code can not be "executed" by Node, then it is not executing TS per definition but something else. If you are good with Node supporting and "executing" only a subset of TS and lacking useful features, that's fine. But don't tell people it is executing TypeScript. That's like me saying my rudimentary C++ compiler supports C++ while in reality only supporting 50%. People would be pissed if they figure it out once they try to run it on their codebase.
> node can find-and-replace type information with spaces from .ts files and try and executing them as if they were plain JavaScript
That’s what all the other tools like ts-node and tsx do already.
I’m not sure what more are you expecting to do?
Typescript is build time type checked, there is no runtime component to TypeScript. If you want type checking you run tsc.
I think this is a great step in the right direction by node. It will save transpiration on the server and improve stack traves and whatnot.
> Once you start using the type system more extensively I suspect this will blow-up in your face.
I don’t see why. There isn’t any more runtime information in “complex”
TypeSceipt types than in simple ones. It’s all build time - see above.
> What a missed opportunity to do it properly
Please explain in more detail what “doing it properly” means to you. Including the typechecker? If so that wouldn’t make sense - they would be competing with TypeScript itself, they shouldn’t, all the “third party plugins” rely on tsc for type checking.
> I think this is a great step in the right direction by node
I think it's the opposite. It will be a net negative, since people will now run TS by default without type checking. Wasting so much time chasing weird runtime errors - just to end up running the full blown TSC type checking again. They will also write very different TS now, trying to workaround the limitation and arguably very useful features like Enums, constructor properties, etc. This has real negative effects on your codebase if you rely on these, just because Node chose to support only a subset.
It's interesting to see the strategy now and to see people even gaslighting people into believing no type checks and less features is a good thing. All just because of one root cause - TSC being extremely slow.
Hmm I think two, since Google pays (paid) Apple to be the default search engine on iOS, it could’ve been said that WebKit and Safari development might have been partially financed with this money.
But I guess that falls apart when we treat Safari as dependent on Apple, which it is.
I wanted to mention MQTT (mqtt.org) as good lightweight protocol that has many implementations.
I was surprised author made no mention of it (mqtt.org) but come to think of it it might be because author is specifically looking for queues it seems and MQTT works better as a PubSub, and its durability story which seems the main focus of the author is way different with very cool features - QoS - for delivery reliability but still not a classic queue
My strategy was to start out by implementing the underlying storage primitives first, and then look into which transport to implement later. The transport of course can have a large impact on the required storage primitives, but in my case I built it the other way around since I knew what primitives I would need in my applications.
I've been playing with the thought of implementing (parts of) the Kafka API, but I honestly haven't considered the transport that much yet :)
Reading, 'ensuring that data is actually written and stays written is rather difficult', immediately reminded me of https://github.com/microsoft/FASTER (its not written in Go though), which is basically dealing with just that outlet ( except I think the KV store might be ram heavy, been a bit since I last looked at it )
Thanks for taking the time to tackle this research.
I think you should mention that „I looked” was done with help of your AI project. That does not spark much confidence given current state of LLMs and their „research”.
From your twitter article:
> So across the ~50 or so prominent whistleblower cases against big co's that I researched with futuresearch.ai, retaliation is common, harassment is rare but does happen, but murder is not.
The big copy on the front page says:
> Your Apple Watch *tracks* VO2 Max—one...
While you have to read through FAQ where you see:
> The watch *estimates* your cardio fitness during outdoor activities and stores it in Apple Health, which our app reads automatically.
All emphasis are mine.
I think it's a little disingenuous to sell this as "Your VO2 Max, finally visible" when it's actually just an estimate from a watch, based on biomarkers. When the real VO2 is measured in a lab with a more involved equipment.
A 2025 validation study involving 30 participants found that Apple Watch underestimated VO2 max by a mean of 6.07 mL/kg/min (95% CI 3.77–8.38) when compared to indirect calorimetry, the gold standard method. The mean absolute percentage error (MAPE) was 13.31%, and the limits of agreement showed considerable variability ranging from -6.11 to 18.26 mL/kg/min [1]. Another 2024 study found similar results, with the Apple Watch Series 7 showing a MAPE of 15.79% and poor reliability (ICC = 0.47) [2].
[1]: https://journals.plos.org/plosone/article?id=10.1371%2Fjourn...
[2]: https://biomedeng.jmir.org/2024/1/e59459
reply