4 ms·
This thread is why I love HN. Thank you. I'm not familiar with Newtons' filesystem. What was different about it? I was too young to have one when it was out an
by tambourine_man 9y ago
This thread is why I love HN. Thank you.
I'm not familiar with Newtons' filesystem. What was different about it? I was too young to have one when it was out and the one I was given a few years ago died.
- mikelevins 9y agoIt didn't exactly have a filesystem; it had an object persistence system for "soups". A soup contained "frames." This Wikipedia describes frames: https://en.wikipedia.org/wiki/Frame_language https://en.wikipedia.org/wiki/Frame_language Newton's frames were much simpler than full-blown frame systems designed for knowledge representation--just mutable finite maps, really. Basically, soups were persistent graphs of maps, (or dictionaries, or hashes, or objects, depending on your language background). Newton apps were also soups. I didn't actually work on the shipping soups. I worked on bauhaus, the Lisp-based Newton OS, which had its own frame system that was a little more like what the Wikipedia article describes, though still simplified when compared to a full-blown knowledge representation system. Apple had one of those, too, by the way. It was called MacFrames, and it was invented by Ruben Kleiman. Both Matt Maclaurin and I had been MacFrames users before getting involved with Newton. MacFrames later evolved into SK8, the Hyoercard-on-steroids project that never made it past management gatekeepers into the wild. I worked on SK8, too, after I returned to Apple post-NeXT, and when I ultimately left Apple it was to go to work for folks that I had met working on SK8. That's yet another story. Those folks founded a startup named Reactivity, where I worked for another 7 years. Some of them are famous now--for example, one of the founders was John Lilly, formerly of Mozilla and now with Greylock; and another was Mike Schroepfer (everyone called him "Schrep") who is now Facebook's CTO. I loved Reactivity, too, but I left it because of a health catastrophe. It was later acquired by Cisco, where, coincidentally, I'm doing some work now. I'm compressing several more tomes worth of stories into the last couple of paragraphs there. I figure I can only ramble so much before it becomes a bore.
- tambourine_man 9y agoRamble on :) You should do a podcast. A Debug episode on that would be really interesting.
- wrs 9y agoThey're called "frames" because Bill Luciw used them like KR frames when he built the Intelligent [sic] Assistant. Built-in dictionaries/hashes weren't a common feature of languages at the time, so I had no better idea what to call them. :) I thought the minimum set of data types you'd need for a usable language is primitives, arrays, and records; frames are how you do records.
- mikelevins 9y agoRight; I remember your discussions with Capps about them in the Living Room. I agree that built-in finite maps were not a common feature of the languges at the time, and that "frames" were a decent word for them. After newton I worked on Ruben Kleiman's SK8 for a while (I had used SK8 when it was still called MacFrames for a personal UI-system project, and then later I worked on Matt Maclaurin's GATE, which also used MacFrames). SK8 was more of a full-blown frame system (plus other things; if Newton's Dylan is my all-time favorite working language, SK8 is my all-time favorite IDE)). The bauhaus frame system was somewhere in-between. It tried to provide a foundation for more frame-system features without actually implementing the more complicated and esoteric ones, like multiple parallel and extensible inheritance systems and truth-maintenance systems and so on. Larry Tesler wrote the initial version of it during his sabbatical, and then I took it over when he, as he put it, "put his executive hat back on."
- osteele 9y agoA couple of “small world” connections: 1. SK8 was implemented in Macintosh Common Lisp (MCL), which was a product of Coral Software in Cambridge, MA. This was one of the justifications for Apple's acquisition of Coral in 1988. Coral became Apple Cambridge, and went on to create Dylan, which was implemented in MCL. 2. There was a period of time where I had moved to California but continued to work on Dylan. Whenever I returned to MA to work out of the Cambridge office, I stayed with my father-in-law, who had originally proposed “frames”.
- mikelevins 9y agoCool! The small-world connections are dense around Apple in general and around Newton in particular.
- Someone 9y agoIt's more of a simple database than a file system. To my surprise, https://manuals.info.apple.com/MANUALS/1000/MA1510/en_US/NewtonProgrammerGuide20.PDF https://manuals.info.apple.com/MANUALS/1000/MA1510/en_US/New... is still up at apple.com. It says: "Object Storage System This system is key to the Newton information architecture. The object storage system provides persistent storage for data. Newton uses a unified data model. This means that all data stored by all applications uses a common format. Data can easily be shared among different applications, with no translation necessary. This allows seamless integration of applications with each other and with system services. Data is stored using a database-like model. Objects are stored as frames, which are like database records. A frame contains named slots, which hold individual pieces of data, like database fields. For example, an address card in the Names application is stored as a frame that contains a slot for each item on the card: name, address, city, state, zip code, phone number, and so on. Frames are flexible and can represent a wide variety of structures. Slots in a single frame can contain any kind of NewtonScript object, including other frames, and slots can be added or removed from frames dynamically. For a description of NewtonScript objects, refer to The NewtonScript Programming Language. Groups of related frames are stored in soups, which are like databases. For example, all the address cards used by the Names application are stored in the Names soup, and all the notes on the Notepad are stored in the Notes soup. All the frames stored in a soup need not contain identical slots. For example, some frames representing address cards may contain a phone number slot and others may not. Soups are automatically indexed, and applications can create additional indexes on slots that will be used as keys to find data items. You retrieve items from a soup by performing a query on the soup. Queries can be based on an index value or can search for a string, and can include additional constraints. A query results in a cursor—an object representing a position in the set of soup entries that satisfy the query. The cursor can be moved back and forth, and can return the current entry. Soups are stored in physical repositories, called stores. Stores are akin to disk volumes on personal computers. The Newton always has at least one store—the internal store. Additional stores reside on PCMCIA cards. The object storage system interface seamlessly merges soups that have the same name on internal and external stores in a union soup. This is a virtual soup that provides an interface similar to a real soup. For example, some of the address cards on a Newton may be stored in the internal Names soup and some may be stored in another Names soup on a PCMCIA card. When the card is installed, those names in the card soup are automatically merged with the existing internal names so the user, or an application, need not do any extra work to access those additional names. When the card is removed, the names simply disappear from the card file union soup."