3 ms·
I feel like we got a “true successor to HyperCard” 20 years ago, in the form of Lotus Notes. It was essentially “HyperCard decks shareable via email, with each
by derefr 7y ago
I feel like we got a “true successor to HyperCard” 20 years ago, in the form of Lotus Notes. It was essentially “HyperCard decks shareable via email, with each deck backed by its own automatically-allocated Firebase-like document DB co-hosted on the author’s email server.”
(And, further, each email client had its own client cert, which it used for 1. code-signing decks it had authored, and 2. signing API requests to the DB server when the deck makes them. So every deck, and every request, would always have a “verified” email address associated with it.)
Essentially, it was the set of functionality provided by Google Sheets + Google Forms (and a bit more), without any web stuff being involved.
Obviously, it became a cesspit of badly-made, overly-interlinked Intranet apps, but this was more to do with the target market of non-IT enterprises—it was no different than what such organizations did with Excel.
I’d really love to see what a system very much similar to Lotus Notes, given a fresh coat of paint, and targeted to consumers, would be used for today. An app anyone could open up and make a little DB-backed interactive experience, then either push it to an in-app inbox of their friends [where it could then be re-shared further, virally] or onto a cloud service others could browse within the app.
- CharlesW 7y ago> I feel like we got a “true successor to HyperCard” 20 years ago, in the form of Lotus Notes. Setting aside that Lotus Notes preceded HyperCard, I'm still missing the connection. Notes seemed to be presented as an enterprise-y workflow tool, while HyperCard was more of a "bicycle for the mind" toy (which I mean in the best-possible sense).
- derefr 7y agoDisregarding the UX, Lotus Notes is just a viewer for HyperCard-stack equivalent app-documents. (There’s no reason they couldn’t have been HyperCard stacks, other than, as you said, the earliest versions of Notes coming first.) Lotus Notes with a different UX would be more obviously just “HyperCard++.”
- al_ak 7y agoI know Alaska used Lotus Domino (a web framework with Lotus Notes as the development stack) in the late '90s to put some of their services online (job postings/electronic applications is the big one I remember). It worked pretty well at the time, but finding Lotus Domino developers isn't easy since it's such a niche product
- derefr 7y agoLotus Domino is, more properly, the database server that Lotus Notes expects to sit beside an email server (making the email+Domino servers, in combination, a "Notes server.") It's the thing that makes Notes not just "HyperCards being sent back and forth." You can think of Lotus Notes as more of a "Domino client" than anything else. All the Notes app-documents authored by a given individual will burn in, as the API-backend endpoint for that app-document, the particular Domino server corresponding to their own originating email server. (It's sort of as if you opened Excel and it automatically detected your company's on-prem k8s cluster, and then installed a workload there for your Excel sheet to reach out and talk to, even when you share the spreadsheet around outside of the organization.) Domino was (is?) a pretty cool and ahead-of-its time piece of tech. In modern terms, it's basically "Firebase as an on-prem appliance." Client applications (i.e. Lotus Notes app-documents) define the schema on connection, rather than there being an explicit out-of-band database/table creation step; and the API handles syncing state between a local representation of the app-document's database and the server's (multi-user shared) representation of same. Or, to draw a parallel from another point in design-space: Domino is like iCloud's Core Data sync, but multi-user (where the data on the server is just an event stream, it's the client's job to linearize+reduce the event stream into a new mutable state, and users take the user credentials that events have been signed with into account in deciding which events have CDRT precedence over which.) Or, for a "ridiculous, but not exactly wrong" analogy: Domino is a private blockchain, and the app-documents loaded into it are smart contracts. Or you could look at it like CouchDB's design documents, with better sync. Really, there are a lot of things you can sort of describe it as, but nothing that perfectly lines up.