Which unfortunately will get moved to NMOS/Future with a P6 priority and ignored forever. At best it'll get sent back to you "for more details". If you play the game an attach logs and investigation it'll get filed make into a black hole milestone or closed as a duplicate. There's a cabal that seems to only want new features and never tackle existing bugs in the OS.
Huh. That sounds strikingly similar to the culture breakdowns I've observed be associated with Google - the whole focus on newness and landing features in the name of solving hard problems, as opposed to maintaining stuff. Apparently the feedback/peer review/bonus system is completely broken.
...Maybe this sort of scaling problem is a "$T+ market cap" thing that we've just never had to figure out before?
> ...Maybe this sort of scaling problem is a "$T+ market cap" thing that we've just never had to figure out before?
I don't know in all honesty. I'm sure part of it has something to do with the fact these companies have billions of customers. It's a mind numbing number of users. Even a single percentile change in the number of customers or revenue per customer makes for huge revenue differences. So given a finite amount of developer effort, a new feature which is likely to increase revenue is incentivized over a stupid AirPlay bug that isn't likely to increase revenue.
1) Customers who barely do anything with their devices and therefore never have issues
2) Fans who experience issues, but accept them as a bump in the road towards the dream they’ve been sold
And this is at a cost-savings: less in R&D (because you can patch in-field), less in maintenance hours, and less opportunity cost for having “10x” devs do that maintenance.
There’s also a fear-based reason for companies to chase features: they worry that the market will see them as stagnant and see the competitors as exciting.
i recall a team that had all its feature releases struck down for the coming year so they would work through their backlog.
Opinions are my own, bla bla bla
I've not had too much issue with wifi performance with several Apple devices on the network, but my wireless router is also a fairly high end consumer model and probably not at all representative of the average.
I do still intend to figure out some sort of hardwiring solution (maybe MoCA, but man those boxes are expensive) but the performance of wifi in the interim has been good enough for it to not be pressing.
Transmit power doesn't matter in that more isn't necessarily better. Same for antenna gain. They are variables you can change if you know you have a specific problem that would be solved by it. That's hardly ever the case, though.
Why not just hardwire CAT6? MoCA is nice if you already have the coax, but otherwise it seems silly to put in.
My house is already wired with unused coax. I’d prefer CAT6, but don’t know how involved doing that would be. I need to figure out if there’s wiring conduits in the walls, for example.
The cause in this case was AWDL (Apple Wireless Direct Link.) Holding the Option key while clicking the Wi-Fi icon and clicking "Enable Wi-Fi Logging" and then checking /var/log/wifi.log will show AWDL scans starting and ending randomly, and when the scan is active it causes latency spikes every 1s like clockwork. Unrelated to AWDL, but if a process is requesting a Wi-Fi network scan (different from an AWDL scan), /var/log/wifi.log will also tell you the name of the process, such as "locationd" when the Location Service needs your location. (Tangential, but the locationd process rarely causes these latency spikes for me - on a default macOS install it very rarely requests scans in my experience, backed by my analysis of the log.)
AWDL has to be used for things like AirDrop, so it's expected to have this latency increase while you have the AirDrop window open scanning for nearby devices / sending files to other devices. There are other uses of AWDL (AirPlay, Auto Unlock, Universal Clipboard at the very least)[0], but I don't know what was triggering it so actively in my case... and why it wasn't happening on my M1 Air. It also wasn't always happening in the background like this, it just started that day.
The "fix" was to disable the awdl0 interface, but that may also cause AirDrop/AirPlay and related services to not function (I did not test.) It's easy to re-enable it though.
To disable: ifconfig awdl0 down
To enable: ifconfig awdl0 up
Upon disabling, the latency spikes go away permanently.
[0] https://owlink.org/wiki/