|
|
|
|
|
by kelnos
1683 days ago
|
|
I think the problem is that making things look to the user as an integrated, polished experience is exceptionally hard when you have the loosest of loose coupling all over the place, and differing views as to how to get things done. Sure, you can put APIs and documented IPC interfaces between things, but that doesn't mean everything will match up in a usable way. So, eventually, you just decide: screw it, we'll own the entire stack, or at least gain enough influence over the people who make parts we don't control, such that everything works seamlessly for us. In part, this is why Apple can give their customers such a polished, "just works" experience. Buy all-Apple gear, and stay in their software ecosystem, and (modulo bugs) everything will work together seamlessly. I don't like this outcome by any means. And I still think that some desktop components certainly benefit from loose coupling and well-defined interfaces, and it's possible to avoid the "polish" downsides in some cases. But doing everything that way, while still being able to put everything together in a polished way, might actually be impossible. |
|