jasim

<!-- 
  When an input element gets focused, iOS Safari tries to put it in the center by scrolling (and zooming.)
  Zooming can be easily disabled using a meta tag, but the scrolling hasn't been quite easy.

  The main quirk (I think) is that iOS Safari changes viewport when scrolling; i.e., toolbars shrink.
  Since the viewport _should_ change, it thinks the input _will_ move, so it _should_ scroll, always.
  Even times when it doesn't need to scroll—the input is fixed, all we need is the keyboard—
  the window always scrolls _up and down_ resulting in some janky animation.

  However, iOS Safari doesn't scroll when the input **has opacity of 0 or is completely clipped.**

jasim

• 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

jasim

type instruction =
  | Order of {id: int; price: float; size: int}
  | Cancel of {id: int}
  | Cancel_replace of {id: int; new_price: float; new_size: int}

let filter_by_oid instructions oid =
  List.filter (function
      o.id = oid
    ) instructions

jasim

Outcome-Oriented Programming

Mike McNeil, Aug 2014

Humans are not very good at planning. We have no problem running scenarios, thinking through possibilities, and pondering "what if?" questions. I might plan to not eat my cousin's birthday cake before she gets home, for instance. If I'm very serious, I might write down my commitment; or if I'm unsure about the pros and cons, use some organizational tool like a T-chart.

But when it comes to making a decision in the moment, all bets are off. The cake is a goner.

Predictive Analysis vs. Process Design

Below, I've included a figure containing a decision tree diagram.

jasim

var ngAppElem = angular.element(document.querySelector('[ng-app]') || document);

window.injector = ngAppElem.injector();
window.inject = injector.invoke;
window.$rootScope = ngAppElem.scope();

Object.defineProperty(window, '$scope', {
    get: function () {
        var elem = angular.element(console._commandLineAPI.$0);
        return elem.isolateScope() || elem.scope();