7 ms·

Yes exactly, and thank you. Imagine if you edited a photo in Photoshop and could only access that edited photo through "Photoshop Live" or some-such. File man

Yes exactly, and thank you. Imagine if you edited a photo in Photoshop and could only access that edited photo through "Photoshop Live" or some-such. File management in the wild is dirty. Either "there is only one" or there is the Clone Wars. This is real. For anecdotal example, a family member had this issue with Picasa [before it was purchased by Google]. "I rotated and cropped thousands of my pictures, but when I look at them in my 'Pictures' folder my edits aren't there. Where are my edits? Why aren't my edits in Picasa in my 'Pictures' folder pictures?" I'm ok being called a pedantic purist on this type of thing. If you want my help, I need to know what you are talking about. Show me your file. If all I am possibly able to see is not what you want, one of us is in trouble.

chrisseaton 7y ago
> For anecdotal example, a family member had this issue with Picasa [before it was purchased by Google]. "I rotated and cropped thousands of my pictures, but when I look at them in my 'Pictures' folder my edits aren't there. Where are my edits? Why aren't my edits in Picasa in my 'Pictures' folder pictures?" But Apple have solved this confusion by removing the files and folders and making the application the one place to do things.
- TeMPOraL 7y ago
  Only if your entire computing is 100% done on your own Apple devices, and you don't need anything beyond the capabilities offered by Apple's software.
  - michaelmrose 7y ago
    God forbid you want to access the same file with different apps.
- drdeadringer 7y ago
  Apple's solution is the problem I spoke about. Putting blinders on a horse allows the horse to behave for the driver. I want the horse to behave like a horse.
htfu 7y ago
Help me understand. Saving yields a psd which indeed requires PS. Whether project lives "inside" app or not it's still bound to it by format, and separate from your source. So you export the edited version, explicitly overwriting your original. Consumer apps don't care when an "edit" means fresh destructive encoding and overwrite, tools like Photoshop do, but that seems a different discussion. I suppose I'm getting hung up on not at all getting/agreeing with your examples. For "regular" files where that project/"edit in progress" distinction doesn't apply (text/code for example), whether edit-in-place is accomplished through system file manager or back and forth across apps through piping and callbacks is just an implementation and workflow detail. I rarely leave the terminal on my laptop, and prefer my stuff always backed up, so that probably what has me predisposed towards the "traditional" iOS cloud storage and x-callback-url approach to working with files and data across apps and gluing them together. It just mirrors nicely. I get that others have different tastes. But what exactly are yours? Files is confusing because there's also camera roll and the difference between On my device and iCloud isn't clear or something? Same for grandparent, just makes little sense in the context of like, iOS 8, close to none for 13.
- TeMPOraL 7y ago
  > Saving yields a psd which indeed requires PS. Whether project lives "inside" app or not it's still bound to it by format, and separate from your source. PSD files can be read by other applications. Not perfectly, but can. Many other proprietary formats have been reversed or opened to the point that other applications can read or edit them. And then there's a whole set of formats that aren't tied to any application per se. No app owns JPG, PNG, WAV or CSV. > whether edit-in-place is accomplished through system file manager or back and forth across apps through piping and callbacks is just an implementation and workflow detail. It's not an implementation detail. The "back and forth across apps through piping and callbacks" is under control of the app developers, and the extent to which it works depends on the contractual deals they sign between each other. A file system is an universal intermediary layer owned by no one, which maximizes interoperability and doesn't require the user to maintain or be aware of relationships between app vendors. (Or, look at it from a software design point of view. If you were presented with large and potentially dynamic network of components exchanging data through APIs, you might actually come up with a file system equivalent as a way of separating concerns and maximizing composability.) > the difference between On my device and iCloud isn't clear or something That would be an important difference to have. Basically, "I'm on a train and Internet is spotty, or my ISP has an outage, will I be able to open and work on this file or not?" is a question for which the answer is kind of critical. The Internet is not electricity, it's not always available.

chrisseaton 7y ago

> For anecdotal example, a family member had this issue with Picasa [before it was purchased by Google]. "I rotated and cropped thousands of my pictures, but when I look at them in my 'Pictures' folder my edits aren't there. Where are my edits? Why aren't my edits in Picasa in my 'Pictures' folder pictures?" But Apple have solved this confusion by removing the files and folders and making the application the one place to do things.

TeMPOraL 7y ago
Only if your entire computing is 100% done on your own Apple devices, and you don't need anything beyond the capabilities offered by Apple's software.
- michaelmrose 7y ago
  God forbid you want to access the same file with different apps.
drdeadringer 7y ago
Apple's solution is the problem I spoke about. Putting blinders on a horse allows the horse to behave for the driver. I want the horse to behave like a horse.

htfu 7y ago

Help me understand. Saving yields a psd which indeed requires PS. Whether project lives "inside" app or not it's still bound to it by format, and separate from your source. So you export the edited version, explicitly overwriting your original. Consumer apps don't care when an "edit" means fresh destructive encoding and overwrite, tools like Photoshop do, but that seems a different discussion. I suppose I'm getting hung up on not at all getting/agreeing with your examples. For "regular" files where that project/"edit in progress" distinction doesn't apply (text/code for example), whether edit-in-place is accomplished through system file manager or back and forth across apps through piping and callbacks is just an implementation and workflow detail. I rarely leave the terminal on my laptop, and prefer my stuff always backed up, so that probably what has me predisposed towards the "traditional" iOS cloud storage and x-callback-url approach to working with files and data across apps and gluing them together. It just mirrors nicely. I get that others have different tastes. But what exactly are yours? Files is confusing because there's also camera roll and the difference between On my device and iCloud isn't clear or something? Same for grandparent, just makes little sense in the context of like, iOS 8, close to none for 13.

TeMPOraL 7y ago
> Saving yields a psd which indeed requires PS. Whether project lives "inside" app or not it's still bound to it by format, and separate from your source. PSD files can be read by other applications. Not perfectly, but can. Many other proprietary formats have been reversed or opened to the point that other applications can read or edit them. And then there's a whole set of formats that aren't tied to any application per se. No app owns JPG, PNG, WAV or CSV. > whether edit-in-place is accomplished through system file manager or back and forth across apps through piping and callbacks is just an implementation and workflow detail. It's not an implementation detail. The "back and forth across apps through piping and callbacks" is under control of the app developers, and the extent to which it works depends on the contractual deals they sign between each other. A file system is an universal intermediary layer owned by no one, which maximizes interoperability and doesn't require the user to maintain or be aware of relationships between app vendors. (Or, look at it from a software design point of view. If you were presented with large and potentially dynamic network of components exchanging data through APIs, you might actually come up with a file system equivalent as a way of separating concerns and maximizing composability.) > the difference between On my device and iCloud isn't clear or something That would be an important difference to have. Basically, "I'm on a train and Internet is spotty, or my ISP has an outage, will I be able to open and work on this file or not?" is a question for which the answer is kind of critical. The Internet is not electricity, it's not always available.