It's not just showing "is the interface up", it's showing current signal strength, showing current ssid, showing results from the recent poll of stations, etc.

And then doing the same for Bluetooth.

And then doing the same for screen rotation and rotation lock settings. And sound settings, And then another set of settings. And another set of settings. All from different places of the system configuration while still having the backwards compatibility of all those old systems.

It's not a slowness on painting it. It can do that at screen refresh rates no problem. It's a question of querying all these old systems which often result in actual driver queries to get the information.

43fps? Sure sounds slow to me. Why not 333fps on that hardware? So bloated, so slow.

You're just listing mechanisms for how it might be slow, but that doesn't really make it sensible. Why would the OS query hardware for something like screen rotation or volume? It knows these things. They don't randomly change. It also knows the SSID it's connected to and the results of the last poll (which it continuously does to see if it should move).

And yes it should cache that info. We're talking bytes. Less than 0.0001% of the available memory.

Things were different on old hardware because old hardware was over 1000x slower. On modern hardware, you should expect everything to be instantaneous.

And yet doing an ipconfig or netsh wlan show interfaces isn't always instantaneous depending on your hardware and the rest of your configuration. I can't tell you what all it's actually doing under the hood, but I've definitely seen variations of performance on different hardware.

Sometimes the devices and drivers just suck. Sometimes it's not the software's fault it's running at 43fps.

I'm hitting the little quick settings area on my exceptionally cheap and old personal laptop. I haven't experienced that slowness once. Once again I imagine the other stuff running interrupting all the OS calls and what not loading this information causes it to be slow.

I don't know what operating system you're talking about, but the bottleneck on my linux machine for asking for interfaces is the fact that stdout is write blocking.

I routinely have shy of 100 network interfaces active and `ip a` is able to query everything in nanoseconds.

Considering this whole conversation is about sometimes some people have a little bit of slowness drawing the quick settings area in Windows 11 and I gave commands like "netsh" it should be pretty dang obvious which OS we're talking about. But I guess some people have challenges with context clues.

And once again, on some Linux machines I've had over the years, doing an ip a command could hang or take a while if the device is in a bad state or being weird. It normally returns almost instantly, but sometimes has been slow to give me the information.