jcsherin

• Side by side terminology of Future and JS Promises to show similarity. This could be setup earlier when Futures abstraction is introduced. The code examples can then instead use JS Promises which should be familiar to frontend programmers.
• References to Finagle are ad-hoc at best in the current draft. Make it clear to the reader how Finagle is relevant to the paper under discussion, and the goals of the project.
• Fix signature difference between Future.t and Js.Promise.t in code examples
• Add an introduction section which sets the context for this narrative. Building a modern web framework which can apply the principles used in building Finagle. Such a web framework written a statically typed language can provide safety guarantees at compile time. The functional style emphasizing immutability, composition, isolation of side effects etc improves our ability to reason about behaviour.
• Rewrite conclusion section.
• Include accidental vs essential complexity quote from out of the

jcsherin

Open Source Codebases

Interactive ReasonML sketchbook

PupilFirst

Programming effectively with types

Effective ML by Yaron Minsky [OCaml]

jcsherin

type t =
  | Object(list((string, t)))
  | List(list(t))
  | Bool(bool)
  | Float(float)
  | Int(int)
  | String(string)
  | Null;