No relation to the sports channel.

  • 9 Posts
  • 1.37K Comments
Joined 1 year ago
cake
Cake day: June 9th, 2023

help-circle





  • 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).


  • Xerox’s prototype desktop computer was called Alto, not X, and had some of these features in a very early form. It was never made into a product for the open market; it was used internally at Xerox and at some research universities.

    Apple didn’t “steal” from the Alto; Xerox invested in Apple and allowed Steve Jobs and Apple engineers to tour their facilities for product ideas.

    You might also be thinking of the X Window System for Unix, whose modern descendant most Linux systems are still using. It’s pretty different from the Mac approach.

    https://en.wikipedia.org/wiki/Xerox_Alto


  • fubo@lemmy.worldtoTechnology@lemmy.worldWhat DID Apple innovate?
    link
    fedilink
    English
    arrow-up
    68
    arrow-down
    5
    ·
    edit-2
    6 months ago

    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 most other systems of the mid-1980s, 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. If you turn the device off (or it runs out of battery power), you don’t lose your work.














  • It doesn’t have to have a copy of all copyrighted works it trained from in order to violate copyright law, just a single one.

    Sure, which would create liability to that one work’s copyright owner; not to every author. Each violation has to be independently shown: it’s not enough to say “well, it recited Harry Potter so therefore it knows Star Wars too;” it has to be separately shown to recite Star Wars.

    It’s not surprising that some works can be recited; just as it’s not surprising for a person to remember the full text of some poem they read in school. However, it would be very surprising if all works from the training data can be recited this way, just as it’s surprising if someone remembers every poem they ever read.