[redeeman]

i like how we are talking about an OS that initially released in 2007, and only got support for "opening files in place" in 2015. What a time to be alive, we can open files in place and all..

gotta give apple credit, while the rest of the world is reduced to lowly CopyOnWrite, they took it one step further, with CopyOnRead.

[scarface_74]

What next? Are you going to complain about Windows not supporting more than 8.3 character filenames until 1995?

[kibwen]

In 2001 people were still complaining about the pervasive usage of 8.3 filenames due to the legacy of Windows: https://slashdot.org/story/01/03/12/210202/why-are-we-still-...

If a given iPad app is still using a legacy API eight years later, that seems worth complaining about. It might not be Apple's fault so much as it is the app developer's fault, although it is at least indirectly Apple's fault for not introducing a proper file management API from the very outset.

[scarface_74]

And no one has named the application in question.

[redeeman]

i would, but thats a bit more forgivable :)

[Doctor_Fegg]

Given that we're in 2023 this seems like a weird hill to die on.

[redeeman]

in 2007 when ios first released, we had the ability to open files without insanities everywhere else. it was total insanity it was not possible, part of the apple thinking that you only do what they 100% say. Who would dare have some video file that isnt in itunes? well certainly not someone the mighty apple cares about. so this lead to movie players also having builtin ftp/smb/nfs clients/servers to be able to access your content, god forbid you could just have files.

so yeah, to have a 2007-vintage API be "legacy that cannot open files properly" is a joke, pretending that it is not, is the apple reality distortion field