Managed I/O Runtime

Hyperfiddle's "functional data-sync" is general-purpose I/O coordinaton infrastructure backed by Datomic.
I/O runtime is an umbrella for several coordinating processes running in various places (jvm, browser, node, AWS Lambda, etc). The secret sauce is the fiddle graph, which lets the I/O runtime introspect the structure and data flows of the application in order to preload data dependencies and serve exact responses. The fiddle graph plus immutability opens the door to many interesting optimization opportunities, and as soon as one person implements one, it can be made available generally to all Hyperfiddle apps. The default I/O runtime is mildly smart.
Different apps have different I/O needs, so I/O runtime implementations are pluggable and swappable. A simple example is you can serve the app completely without javascript and rely only on server side rendering, as is the case of this documentation (view source to confirm). The administration side of this docs app has javascript, datagrids, etc (for example!index/)
Here are some ideas of what you could build in a custom I/O runtime and plug into any Hyperfiddle app:
  1. Getting Started
  2. Overview
  3. Tutorial
    1. Simple blog
    2. Seattle
  4. Concepts
    1. Design
    2. Technology Vision
    3. Data model
    4. Semantics
    5. Staging area
    6. I/O Runtime
    7. Transactions
    8. Foreign integrations
    9. ctx
  5. Guides
    1. Links
    2. Transactions
    3. Dependent queries
    4. Iframes
    5. Select options
    6. Semantic admin console
    7. hyperfiddle.ui
    8. Markdown
    9. CSS
    10. Users and permissions
    11. Migrations
    12. Bulk import
  6. Triage
    1. Architecture braindump
    2. Technical braindumps
    3. hyperfiddle.jar