Interesting rgd. the functional reactive programming. I am obsessed with this, in a networking/mobile device context instead of a gaming context - not that it should matter. And applying this to real problems beyond the toy problems that you find in tutorials on the web turns out to be real hard - this may end up becoming my Forever Project yet. Email me at hank[at]ml1.net if you want to discuss this.
That said, I'm not entirely sure about the definition of M2 and how that's related to 'money sitting in the bank'. M2 includes 'savings and time deposits' according to Wikipedia, but it doesn't seem to differentiate whether banks in turn lend out that deposited money or it just sits there.
I didn't find his reasoning in favor of raising the ceiling very convincing. It's just saying "these people are in favor too", and it's all the usual suspects with vested interests. That doesn't make them wrong but just not very convincing.
What does make not raising the ceiling very convincing is that it's called a 'ceiling' and it's not a ceiling if you raise if every couple of weeks as seems to be the fashion, it's been put in place by wise men of the past to keep repeating previous mistakes and Greece shows what happens if you don't have a ceiling.
- Should it be out of service for a short time, it'd be disrupting my workflow.
- Should it be out of service for a long time, I'd have to move to a different server and risk losing contacts that only know me by my github name/URL.
- Most importantly: On my server I have repos that are more open that 'private' but less open than 'public'. E.g. I hand out invites to a repo to attendees of a meeting. Or I limit by location using geo-IP.
I use git-backed wikis for the 'conversation' part. Project mailing lists are wrong for the same reason that Subversion/CVS were wrong: Centralization turns a project political, at least that's my experience. Git's distributed storage encourages forking at a whim. If your 'conversation' is via a wiki you can fork that conversation any second.
Git-backed wiki how-to: My "wikis" currently simply are HTML pages served by gitweb right out of the repo, however I am experimenting with gollum and smeagol. That is: if your repos are on some server of your own, not github. I have no exprience with github and won't be caught dead using it.