this post was submitted on 19 Dec 2023
161 points (81.3% liked)

Technology

60107 readers
2060 users here now

This is a most excellent place for technology news and articles.

Our Rules

  1. Follow the lemmy.world rules.
  2. Only tech related content.
  3. Be excellent to each another!
  4. Mod approved content bots can post up to 10 articles per day.
  5. Threads asking for personal tech support may be deleted.
  6. Politics threads may be removed.
  7. No memes allowed as posts, OK to post as comments.
  8. Only approved bots from the list below, to ask if your bot can be added please contact us.
  9. Check for duplicates before posting, duplicates may be removed

Approved Bots

founded 2 years ago
MODERATORS
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
161
What DID Apple innovate? (lemmy.world)
submitted 1 year ago by [email protected] to c/[email protected]
341 comments fedilink hide all child comments
 

Genuine question.

I know they were the scrappy startup doing different cool things. But, what are the most major innovative things that they introduced, improved or just implemented that either revolutionized, improved or spurred change?

I am aware of the possibility of both fanboys and haters just duking it out below. But there's always that one guy who has a fkn well-formatted paragraph of gold. I await that guy.

you are viewing a single comment's thread
view the rest of the comments
[โ€“] [email protected] 2 points 1 year ago (1 children)

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.

[โ€“] [email protected] 1 points 1 year 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).