| yes I want to reemphasize coldtea's point. These resource forks are part of the core platform and the tools that need to use them have the code to be able to manipulate them. Anyone who's ever worked with Macs - including software writers, tool writers, developers, know about resource forks - and it's fine because major tools have been rewritten to be resource fork aware. Nothing's really gone wrong in the sense of reality and while there may be hiccups, you don't really see users actually complain about resource forks. It's the hypothetical case where "people actively start storing critical data ..." etc. In this case, those people haven't done their homework about the mac platform. Like the Original Post of this HN thread - this person clearly hasn't read the docs re: resource forks and is hacking around, assuming that the mac should be like any of the platforms they've used before, and complaining when it is different. There are also extensive - majorly detailed documentation from Apple themselves re how resource forks are used and in which circumstances: https://developer.apple.com/search/?q=%22resource%20fork%22 That gives a ton of hits. Just read the docs. Really. Again, I pull out the old Windows example moving from FAT to FAT32 8.3 filenames -> Long filenames contains a backwards compatible way to truncate long filenames back down to 8.3. So what if someone stores critical information in the long filename that is suddenly lost when round-tripping through an OS that doesn't understand long file names? SHOCK!! HORROR! Reality is no one does that. End of story. https://en.wikipedia.org/wiki/Long_filename Platforms are different! just learn what's different so that you don't get caught unaware. |