Does anyone have any insight into how much benefit MSFT actually gets from these decisions? I understand that the intent is to 'make line go up', but as a simpler user I can't really imagine how telemetry and shilling OneDrive actually leads to meaningful revenue growth. On the other hand, people have been loudly complaining about this since the Windows 7 days, and I imagine that there must be some reason they're doubling down on such an unpopular strategy.
> I can't really imagine how telemetry and shilling OneDrive actually leads to meaningful revenue growth.
Microsoft’s ad revenue is $10B (1). Allowing advertisers to send ads based on user profiles is a major feature of digital advertising. Collecting telemetry data improves the user profiling.
These types of changes have a direct positive impact on one of Microsoft’s fastest growing revenue stream. This will lead to meaningful revenue growth.
Former MSFT here. People tend to think of Microsoft as one unified company with a unified strategy.
That is not the case, its best thought of as a batch of little companies that band together to create a product. These companies may compete for resources and attention internally and so each one will optimize for their own benefit.
Ads in Edge? That's probably a decision made by some Principal Program Manager with director support on the browser team. The metrics that get tracked for that event are likely how many people click through the ad, rather than the over all impact to the OS.
The OS Core team doesn't have the influence to say no, or stop the browser from showing those ads. I recall internally when I (a paying customer for O365) got a toast (that is what a popup ad is called internally) for O365 and I decided to raise an issue.
Some PM II (mid-level PM was running the campaign, and they were showing metrics that more people signed up for O365 as a result of the campaign, so per them it was good. I was not in that organization and since that director had OKRs that required signups, he told me to go away.
The core OS stripped down has none of these things, but at integrated build, lots of stuff gets put in, and when one team says no to something, often another one will say yes. A good example is that Office has its own update infrastructure and tooling outside of Windows Update. Why? Office wanted to deliver updates on weekly basis and Windows Update said no as that would be too impacting for users, so Office simply said ok and built their own.
These issues rarely if ever get surfaced to an executive, as by the time the metrics get up to a CVP generally they are showing broader trends, like adoption, or game breaking bugs, or as you note, the line going up. Executives do not get these problems (such as inconsistent UI) to them. Those things rarely rise above a Group PM or Engineering Manager level, and those people often do not care about the complaint as for that metric helps them or is part of their strategy.
Windows, the product team cannot do anything about it due to political problems internally at MS and that is not the engineering team behind Window's fault. We (as that was a team I was on) hated when a product team would do something obnoxious and if we could catch it prior to release would often bluntly complain. More often than not we would get told that we were the platform and to stay out of the other teams business.
Anyways, there isn't some mass company dark pattern strategy or other conspiracy, just a bunch of little factions that are all optimizing for their own interests. Office is probably the worst offender of the batch (Skype, Teams, OneDrive) and Windows can do little about it.
I'd argue that once a movement has been installed it's very difficult to rule it out unless someone on the board can PROVE that it hurts revenue. This kind of decision (UI designers overriding anyone else) probably comes from a middle manager who has top support, the exact reason why it is impossible to un-stuck such decisions. Think Apple, you have to get X out before you can unstuck his/her decisions. That's politics.
I didn't understand that either, but I found a good explanation on page 2:
"The fair use question is a mixed question of fact and law. Reviewing courts should appropriately defer to the jury’s findings of underlying facts, but the ultimate question whether those facts amount to a fair use is a legal question for judges to decide de novo. This approach does not violate the Seventh Amendment’s prohibition on courts reexamining facts tried by a jury, because the ultimate question here is one of law, not fact. The “right of trial by jury” does not include the right to have a jury resolve a fair use defense."
Good point. I think the what's missing is how electron energy states work in quantum mechanics. The wikipedia paged (linked below) has a pretty good explanation:
"A quantum mechanical system or particle that is bound—that is, confined spatially—can only take on certain discrete values of energy, called energy levels. This contrasts with classical particles, which can have any amount of energy. The term is commonly used for the energy levels of electrons in atoms, ions, or molecules, which are bound by the electric field of the nucleus, but can also refer to energy levels of nuclei or vibrational or rotational energy levels in molecules. The energy spectrum of a system with such discrete energy levels is said to be quantized". (https://en.wikipedia.org/wiki/Energy_level)
To put things another way: while there could theoretically be infinite sizes of energy quanta, the permutations of energy states for matter are in fact discrete.
What you say is true, but also incomplete. We are perfectly able to quantify the accessible states in purely classical systems, such as ideal gases, without requiring discrete energy levels. The trick is to think of a continuous probability density instead of discrete probabilities. This framework is very general and does not depend on the quantum-ness of what you look at.
Even in some systems that actually follow quantum mechanics (such as phonons or electrons in a material, or photons in a black body), we often use continuous probabilities (densities of states) because it’s much more convenient when you have lots of particles.
I've had a very good experience with Strongbox. I personally haven't used the Nextcloud integration yet so I can't vouch for that specifically, but I've used it with multiple cloud services and it's been seamless every time. It also caches your database locally, which should solve the problems you were having with BoxCryptor. It is freemium, and the really useful features will cost $1 per month, but there is also an option to purchase a perpetual license. Quality indie apps are hard to come by iOS these days, and I'm glad to pay for a service that's so integral to my daily life.
