I missed resource forks when they moved to the UNIX way in what's now macOS.
You could mod Windows apps the same way (and at least one resource editor was also named ResEdit), yet the filesystem didn't provide multiple forks --- it was just a separate section in the binary.
In fact macOS apps are just a directory containing both the main binary and resources.
I remember Borland’s resource editor. I themed my VGA.DRV file quite extensively.
Later on, Windows NT gained resource forks. An early security flaw of IIS was that you could ask it to serve the DATA fork of any source file and see things like hard-coded credentials (because IIS would not execute the file, just serve its contents).
> In fact macOS apps are just a directory containing both the main binary and resources.
This is a much saner design decision, but it wouldn’t be possible before the file system got folders.
Forks caused all sorts of issues when you needed to transmit a file from one computer to another without using a floppy disk.
You could mod Windows apps the same way (and at least one resource editor was also named ResEdit), yet the filesystem didn't provide multiple forks --- it was just a separate section in the binary.
In fact macOS apps are just a directory containing both the main binary and resources.