btholt

const React = require('react');
const _ = require('lodash');

var model = new falcor.Model({
  cache: {
    movies: [
      {
        title: "Daredevil",
        plot: "Marvel lol",
        year: "2015-",

ohanhi

Learning FP the hard way: Experiences on the Elm language

by Ossi Hanhinen, @ohanhi

with the support of Futurice 💚.

Licensed under CC BY 4.0.

Editorial note

bhauman

Recent improvements to the ClojureScript compiler have greatly simplified setting up development versus production outputs.

This example uses Figwheel as something that you want to exclude for production, but the pattern is general.

With this simple setup you only need one html file/view and it will work for developement and production.

ryanflorence

var Authenticated = React.createClass({
  statics: {
    willTransitionTo (transition) {
      if (!authenticated()) {
        transition.redirect('login');
      }
    }
  }
});

panozzaj

"town:King":
  states:
    initial:
      condition: (gameState) ->
        !gameState.magicKey and numTimesTalked is 0
      transitions:
        talk: "followUp"
      action: ->
        dialog [
          """

mwhite

The Ultimate Git Alias Setup

If you use git on the command-line, you'll eventually find yourself wanting aliases for your most commonly-used commands. It's incredibly useful to be able to explore your repos with only a few keystrokes that eventually get hardcoded into muscle memory.

Some people don't add aliases because they don't want to have to adjust to not having them on a remote server. Personally, I find that having aliases doesn't mean I that forget the underlying commands, and aliases provide such a massive improvement to my workflow that it would be crazy not to have them.

The simplest way to add an alias for a specific git command is to use a standard bash alias.

# .bashrc