Component: Ideas to Try Out

This Issue is a grab-bag dumping ground for a bunch of Dark ideas that we'd like to not forget about, but aren't high enough priority to seriously consider yet. If users submit Issues that seem really interesting but would fill up GitHub Issues, we might link them here, close the issue, and reopen it once we're able to tackle it.

• Allow users to comment on functions, like in the old days of PHP (eg see "User notes" in https://www.php.net/strip_tags)
• WebSockets support (see #4046)
• support user-defined languages (ambitious, uncertain, hard)
  • build langs on and in darklang
    • user provides AST, grammar, etc
    • all gets compiled to some darklang bytecode (or interpreted) at end of day
    • distributed treesitter (waves hands vaguely)
• a web-hosted terminal emulator that can run Dark CLI apps
  • probably xterm.js
  • an officially-supported page where our users can log in
  • allow our users to define their own CLIs hosted like this
  • probably needs WASM runtime to come back in, and house the language server? or it could all be over HTTP
• something like jq, in dark
  • type Error = CouldNotNavigate of pathSoFar: List<JsonPath> * failureAt: JsonPath.Part
  • let navigate (json: Json) (path: JsonPath): Result<Json, Error> = ...
  • could wrap that such that:
  • json |> Json.Nav.accessField "fieldName" |> Json.Nav.accessIndex 4
• Add support for Mustache template system (see old #3354)
• support seamless RPC between Darklang CLI installs (see here)
• we have this old post where we advertise you can "build a slack app in seconds with Dark" but immediately say it's a bit of an exaggeration. Let's make it not an exaggeration. From signup to slack app in < 1min.
• some sort of GraphQL support

No file, test, or entry point is identified. This issue is a stale grab-bag of unrelated ideas, so start by choosing one proposal and locating its relevant subsystem before defining separate scope, acceptance criteria, and tests for that idea.