5 ms·

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

by Spivak 3y ago

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 browser okay to tightly integrate but not Edge? The whole OS is a mess of tightly coupled software with messy boundaries. I don't think the coupling is the thing that matters.

clhodapp 3y ago
Dolby Atmos, at least, sounds good but it's pretty annoying because it's had the practical effect of making height channels proprietary in most systems. Springboard definitely isn't OK. There's no good reason that Airdrop shouldn't be in the Linux kernel and it probably would be if the protocol were well documented. You can use game overlays other than the Steam one, so there's nothing stopping Microsoft from creating an overlay that provides the Edge browser. Rich integrations are great but when the boundary is perceived by the user as being two different programs or systems, both sides of the integration should have well-documented public interfaces that support swapping out the other side (no "private API" funny business).
hakfoo 3y ago
"Tightly integrated" can mean "We designed A and B to fit together well. We built them side by side and tested them together" That's perfectly acceptable and can make a fair direct case to the customer. 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.

by Spivak 3y ago

clhodapp 3y ago

Dolby Atmos, at least, sounds good but it's pretty annoying because it's had the practical effect of making height channels proprietary in most systems. Springboard definitely isn't OK. There's no good reason that Airdrop shouldn't be in the Linux kernel and it probably would be if the protocol were well documented. You can use game overlays other than the Steam one, so there's nothing stopping Microsoft from creating an overlay that provides the Edge browser. Rich integrations are great but when the boundary is perceived by the user as being two different programs or systems, both sides of the integration should have well-documented public interfaces that support swapping out the other side (no "private API" funny business).

hakfoo 3y ago

"Tightly integrated" can mean "We designed A and B to fit together well. We built them side by side and tested them together" That's perfectly acceptable and can make a fair direct case to the customer. 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.