The document-centric model of desktop applications largely originates from the early Mac. How do you open a document in a desktop OS? You double-click on the document, and the OS finds the correct application to open it with. That was a Mac thing. On PC systems at the time, you run your application program (from the command line) and then tell the program to load a file.
Applications as “bundles” of code and data was a Mac thing too, starting with the resource/code division in the classic Mac System. Rather than an application coming with a mess of directories of libraries and data files, it’s all bundled up into a single application file that can contain structured data (“resources”) for the GUI elements. On a classic Mac, you could load an application program up in ResEdit and modify the menus, add keyboard shortcuts, and so on, without recompiling anything.
The Apple Newton had data persistence of a sort that we now expect on cloud applications like Google Docs. Rather than “saving” and “loading” files, every change was automatically committed to storage.
ripcord@kbin.social 11 months ago
Other systems did have double-click, and app bundles (which I still think are just fantastic) were a NeXT thing. (which of course became Apple, but they weren't at the time). But yeah, Apple way refined and brought those to a mass market.
abhibeckert@lemmy.world 11 months ago
Apple and NeXT had all the same people working for them.
ripcord@kbin.social 11 months ago
App bundles have virtually no relationship with resource forks. I guess you could say that App Bundles COULD include SOME metadata that you could have included in Forks, including the idea that something was an application or not. But that's about it.
On the NeXT always being Apple thing - I mean, some of it maybe was spiritually Apple, and eventually it was 100% Apple. But we're splitting hairs.
fubo@lemmy.world 11 months ago
Eh, the difference between app bundles and resource forks isn’t the functionality itself, but rather how the filesystem interface cuts through the functionality.
An OSX bundle is a Unix directory, whereas a classic Mac application is a file in a filesystem that supports multiple forks within a single file. Either way, you have typed objects (files or resources) that get carried around with a master object (the application).
fubo@lemmy.world 11 months ago
The first Mac came out in 1984; NeXT didn’t have a product until 1988.
NeXT was later bought by Apple and their tech became the foundation of Mac OS X in 2001.
But I was referring to the original '80s Macintosh System, not OS X. :)