sdfhbdf

It's a little perplexing. Of course it's always a controversial topic since it's difficult to value an exploit, but whenever we read about these online, which probably goes through some survivorship bias, they seem pretty low.

> SubmitQueue speculatively rebases and validates multiple changes in parallel against predicted future states of HEAD. When validations pass, changes land automatically. When they fail, SubmitQueue isolates the offending change and retries the rest — all without human intervention.

This seems to be a feature of GitHub (We have it in an old enterprise server installation) that does the same thing:

> When a pull request is added to the merge queue, the changes in the pull request are grouped into a merge_group with the latest version of the base_branch as well as changes from pull requests ahead of it in the queue. GitHub will merge all these changes into the base_branch once the checks required by the branch protections of base_branch pass.

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?

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.

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].