Because the local LLM, which you are not running, is running for much longer than gcc and is eating the battery. Different choices, different outcomes.
Bur the implication here in the parent comment is that for ‘real dev work’ to be done you must be running an LLM, and therefore you can’t do it on a MacBook anymore.
Turns out you can still accomplish stuff with a text editor and compiler.
Of course we can code without a LLM, but if we want to, as the sibling comment says, don't run a local LLM on a laptop. I'm offloading the LLM to the LLM vendor, like most of us IMO. The CPU is still busier then it used to be, because of the local harness.