![]() ![]() ![]() Given that Adobe software costs a lot - quite a bit more than the price of the entire OS - Mac users are justifiably looking to Adobe to solve this integration problem.Īs a followup to the workaround by unchecking "Icon" in the prefs. ![]() The expectation is that it shouldn't even have been released with this problem in it. THEY aren't expecting to have to even deal with the problem, much less do things to work around it or do without the functionality. There are even free solutions out there.īut Mac users expect it to "just work", without their attention. Case in point: The lack of thumbnails provided by Photoshop and Windows Explorer can be corrected by a 3rd party codec pack. PC users would more likely take such an issue in stride, and perhaps go on a search for a 3rd party solution which either replaces the functionality of the OS or augments it, or works around the problem. So here we have an integration problem - one in which apparently Adobe hasn't been able to find a workaround to an Apple system problem, and also apparently which defies oversimplification. Even Apple's subsystems facilitate a higher level of application integration in general. PC users plop their own drivers in, Apple users get them from Apple, after Apple has tested and approved the release. And rightfully so - it's an extension of the "it just works" philosophy.Īpple themselves integrate many things, such as the working of the display driver (made by nVidia or ATI) and OSX. They don't expect to have to take on the task of integrating things themselves. There's an interesting dynamic playing out here.Īpple users expect the things they do on their systems to be well integrated. ![]()
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |