When the Swish service launched (2012) it was only consumer-to-consumer and no fees. Last year they added businesses and charge similarly to credit cards, fee on the creditor side.
I changed from the ternary representation to the function, because I didn't think the generated code was very readable. In hindsight I'm not sure it's that much improvement. From a performance view it's probably worse off.
The code examples doesn't use Jane Streets Core as the primary standard library. If you do, for example by adding `open Core.Std` to your .ocamlinit, you'll get the behaviour you're describing.
It is probably a good idea to use Core, but for this introduction I wanted as little requirements as possible.
What is it that's missing in just using plain React (with Mori or any alternative)?
In my mind, what Om is bringing to React is idiomatic state management with Clojure semantics. In js I think the local state model promoted by React is reasonable.
Can't you negotiate the terms with your clients? I know that at least my clients have been open to that.
Perhaps not what you want to hear, but other that getting paid more quickly, the most obvious solution to cash flow problems is having a large enough buffer.
I've switched to using Ansible for this very reason (after getting frustated with Puppet) - I like it a lot. Also I just want to join the choir: Vagrant is awesome!