The Challenges of Integrating the Unix and Mac OS Environments (2000)
1–10 of 35 posts
Re: The Challenges of Integrating the Unix and Mac OS Environments (2000)
#2I still remember being in awe that they pulled this off at all, clumsy as some of the compromises were.
Newer filesystems and application designs have eliminated many of the differences, although I still miss resource forks.
Re: The Challenges of Integrating the Unix and Mac OS Environments (2000)
#3Does anyone else remember when MacOS marketing made UNIX a significant part of its sales pitch? I remember a giant, titanium UNIX logo
Re: The Challenges of Integrating the Unix and Mac OS Environments (2000)
#4I still remember being in awe that they pulled this off at all, clumsy as some of the compromises were. Newer filesystems and application designs have eliminated many of the differences, although I still miss resource forks.
I feel the modern approach takes the main strengths of resource forks and builds on them—instead of needing to use ResEdit, all of your application resources are just ordinary files stored in a directory. Images are stored in standard formats like PNG, data is often stored in plist or text formats.
Re: The Challenges of Integrating the Unix and Mac OS Environments (2000)
#5"Sends other UNIX boxes to /dev/null"
Re: The Challenges of Integrating the Unix and Mac OS Environments (2000)
#6I still remember being in awe that they pulled this off at all, clumsy as some of the compromises were. Newer filesystems and application designs have eliminated many of the differences, although I still miss resource forks.
I feel the modern approach takes the main strengths of resource forks and builds on them—instead of needing to use ResEdit, all of your application resources are just ordinary files stored in a directory. Images are stored in standard formats like PNG, data is often stored in plist or text formats.
True, I do like 'Show Package Contents'
Re: The Challenges of Integrating the Unix and Mac OS Environments (2000)
#7I still remember being in awe that they pulled this off at all, clumsy as some of the compromises were. Newer filesystems and application designs have eliminated many of the differences, although I still miss resource forks.
I feel the modern approach takes the main strengths of resource forks and builds on them—instead of needing to use ResEdit, all of your application resources are just ordinary files stored in a directory. Images are stored in standard formats like PNG, data is often stored in plist or text formats.
Maybe somebody who knows classic Mac well can correct me here if I'm wrong, but I feel like resource forks were also solving a "constrained memory and an OS that didn't do paging" problem.
So the library deciding how to load and possibly when to evict sounds like it was kind of the point. Simulating what might be the job of mmap() on a modern system.
Re: The Challenges of Integrating the Unix and Mac OS Environments (2000)
#8Does anyone else remember when MacOS marketing made UNIX a significant part of its sales pitch? I remember a giant, titanium UNIX logo
Yes, they got it certified with 10.5, I think. Small market these days, although I'm always surprised when I hear that both AIX and HP-UX are still receiving updates...
Re: The Challenges of Integrating the Unix and Mac OS Environments (2000)
#9Does anyone else remember when MacOS marketing made UNIX a significant part of its sales pitch? I remember a giant, titanium UNIX logo
It worked on me! I bought a PowerBook G4 in 2003, when I heard Fink/MacPorts and Jaguar were no longer complete nightmares to use. Been Mac only since then.
Re: The Challenges of Integrating the Unix and Mac OS Environments (2000)
#10I still remember being in awe that they pulled this off at all, clumsy as some of the compromises were. Newer filesystems and application designs have eliminated many of the differences, although I still miss resource forks.
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.