Jess's Lab Notebook

Files are the future

Examples of File-rich Ecosystems

File over app

  • what kinds of files qualify? Does it have to be human readable?

  • when is a file not enough?

  • What about collaboration?

  • Seems like files are good because there are at least multiple readers?

  • It’s less about the file itself than the code to read/edit the file

    • “Incredible journey” startups that give you a json dump
  • files as interop

    • Multiple readers / writers and use the file system as the sync layer and read/write layer
  • feels like he’s cheating because text files are encoded! They are ansi text

  • What about automerge documents as “files”? You can save them to the file system, they are richer and have history and all

  • what he’s really saying is “use plain-text as the encoding for all data” and “use a file on the file system as the container”

  • Separate the principles from the implementation...

  • Files got their asses kicked

  • desirable properties are places not things

    • key to a place where you can go to a collaborate
  • have a place

  • qualities of materials

Files are the future
Interactive graph
On this page
Files are the future
Examples of File-rich Ecosystems
File over app