You could do this today on Windows with NTFS Alternate Data Streams.

Windows also supports "resources" (menus, icons, etc.) that can be compiled and linked into the executable.

Resource forks died out because users want to easily see where data is hiding, and having multiple files attached to the same name didn't make the filesystem fast or manageable.

Resource bundles (borrowed from RISC OS) allowed hiding the resources in the Finder by presenting them as an app, but also making it easy to open the Contents folder and see the internals

> Windows also supports "resources" (menus, icons, etc.) that can be compiled and linked into the executable.

One crucial difference is that the Mac OS resource fork is dynamic - the system provided methods to create and modify resources at runtime, and many applications did so. Windows resources, by contrast, are static.