Problems with state

state-pitfalls.js

function Closure(args) {

var refState = args[0] //some state by referencing

//completely new state
var newState = {
  order: 1
}

//when objects are passed around they might end up cached elsewhere
doSomethingWithState(refState, newSate)

//getting rid of cached state is not really possible
refState = null;

//let's assume we forget to do this
//newState = null;

//this will have references to some state
return function() {
  if (newState) { 
    alert(1);
  }
}

}

sure - the nice thing about values vs a mutable object is that once you have a reference to it, you know it'll stay that way. there's no way you'll check it again and it'll have an invalid value etc