News for hackers. Stuff that matters.
Re:The Challenges of Integrating the Unix and Mac OS Environ... by donatj on Wednesday March 10, 2021 @11:50AM (#26413260)
Correct me if I'm wrong here, but macOS still has resource forks, right?

My understanding is that's where file tags, file comments and custom file icons are stored.

Re:The Challenges of Integrating the Unix and Mac OS Environ... by rvense on Wednesday March 10, 2021 @12:00PM (#26413399)
Maybe, but Mac APIs don't use them, so you can't mod your games with ResEdit anymore.

NTFS also has multiple forks, and also has many of the same fancy attributes capabilities that made the BeOS filesystem (in)famous, but they're not used in the same way, so it's kind of moot.

What really what made BeOS and Mac OS good was not so much the technical underpinnings, but the way they exposed these in the APIs and standard applications.

The power of Unix isn't just from the presence of the standard I/O routines, but the fact that most programmes are written to adhere to a specific paradigm that allow them to work together.

Re:The Challenges of Integrating the Unix and Mac OS Environ... by grishka on Friday March 12, 2021 @01:56PM (#26439444)
It has extended attributes instead. You can look at them with `xattr -l /path/to/file`. Tags go into `com.apple.FinderInfo`, and resource forks are, predictably, `com.apple.ResourceFork`, though they're probably still stored in a format classic Mac OS understands.