I'm curious why Microsoft has that setting on by default. What are the benefits of letting any peripheral make system level changes to that extent without popping up a user installer?
Users don’t have to laboriously track down the drivers for a new peripheral and manually install them. It enables almost any device to become plug and play. But it needs guard rails.
One of the primary purposes of batching is to release features at a regular cadence, and all releases go through the same minimum set of checks to catch any unexpected regressions.
In my experience, the workload of these checks grows much slower than linearly with batch size.
I think the article is mostly just confusing throughput and latency. Releasing on a fixed schedule adds some latency, but that doesn't mean there's a bottleneck constraining throughput. And long-term, development speed is determined by throughput, not whether you shipped a feature a few days earlier.
High latency might become a problem if you need user feedback to decide what to work on next, but you don't necessarily need to push everything to production immediately to get feedback. You can have a separate beta/staging system and ask users to check out your new changes there before they get rolled out to everyone.
The data on the results section shows almost parity between the control group and participants who discontinued for 2 years.
Note that while it is a well conducted study at the US VA with 300,000+ patients, it is not a randomized study so fully eliminating confounding variables and reverse causality is hard.
reply