Because it's enough to look at modern Windows and things like "CPU spikes 100s of percent when opening start menu because it's now written in React"
I am sure that the Power team has the understanding that user-initiated activity isn’t really anything they can control.
Once the user takes over, all tricks for efficiency go out the window. The user could run anything.
I don’t work for MS but I’m sure the Power team cares about the automatic built-in stuff that runs on schedules and timers: the things they can control. The start button doesn’t click itself.
I agree that using web tech to render things in the OS is silly, but Microsoft has been doing it in every Explorer window since 2001 with Windows XP. I don’t remember anyone complaining about that at the time except me.
> Once the user takes over, all tricks for efficiency go out the window. The user could run anything.
Erm. In case of the start menu and task bar, where they are pretending that showing servings is an issue, they do have control of a lot of things.
Somehow they split hairs over showing seconds, but are perfectly okay with web views in the task bar and in the start menu, and are perfectly okay with components in React Native.
> I agree that using web tech to render things in the OS is silly, but Microsoft has been doing it
Yes, they have been doing it. Somehow the "power team" that supposedly had ultimate control over what gets displayed had no issues with that
I wouldn't be surprised if there were some misalignments in goals though. E.g. if their team's goals are measured in results of typical battery life tests such as "how many hours the computer can sit idle playing a video" then they would be heavily weighted towards caring about these kinds of constantly recurring background draws instead of active usage draws.
Yeah, it's very likely "metrics- driven development" when optimizing certain metrics becomes its own isolated goal