Earlier quoted context omitted.
> Somehow we need to find a balance that allows vendors to tightly integrate their apps but prevent abusing this A vendor of a web browser and email client, sure. A vendor of an operating system and one (or both) of a web browser and an email client, hell no. If anything, an operating system should be forced _not_ to tightly integrate to vendor-specific apps and instead should provide integration loosely and in a way…
I do think people like Dolby Atmos, Android Auto, Airdrop, SMB, systemd, the whole of SteamOS and I think when you get down to it "tight integration but I don't like it" is the only definition you'll get that actually will encompass what people mean. Because what makes Springboard on iOS okay when on Android you can have Nova? What makes NFS okay to build in the kernel but not Airdrop? What makes Steam's overlay brow…
What's not:
* Not allowing controls to manage integrations. Maybe I want to connect A to C, D, or Q instead, or not allow a connection at all.
* Accidentally-on-purpose clobbering customer choices (ooh, whoops, we reset all your file associations for the sixth time this year, perhaps now you'll stop changing them).
* Using undocumented APIs or similar gimmicks to ensure a competitive product will be inherently hamstrung.
* Pretending a seperate product is an indivisible component of the whole. I'm sure there are a bunch of places where Edge could be pulled out in favour of an external help-file/PDF/etc viewer.