He has a YouTube channel where he has some "5 Minute" code walkthroughs where he analyzes randomly selected code and its context, and tries to explain it. The few that I've watched had a fair amount of rambling, and since it's random, it's obviously not a structured overview... but still interesting.

http://www.youtube.com/channel/UCdX4uJUwSFwiY3XBvu-F_-Q

I think it's the intersection, so, "and".

P(A|B,C) is "Probability of A, given both B and C".

That's true, may be a slightly confusing way to interpret it, given that C = A∪B. In context I think it's better to read it as P(A|B), in the case that C occurs.

wouldn't that be P((A|B)|C) ?

or even more precedence dubious: P(A|B|C) ?

The "given" symbol should only appear once in any probability statement.

That's true from an objective, mathematical standpoint. But the paradox is really saying something about how humans perceive the statement, so different (mathematically equivalent) ways of framing the same thing can make a difference. It's a minor point.

I don't know that I'd compare it to Scala at all, I feel like they have very different capabilities, each of which have their pros and cons.

Whether it's uglier... I guess I haven't written enough Scala to know, but my Scala is pretty ugly :(.

Scala is at it's prettiest when you use a mostly-functional style, but use imperative style when it's substantially easier/shorter/more readable, in my opinion. The most important thing is to have your functions be as pure as possible and their return objects be immutable. What happens inside them is less important.

It's worth noting that few, if any, modern languages let you write as ugly code as Scala does. Take mutable objects with inscrutable loops and couple it with spaghetti recursion? Scala doesn't mind....

We use a bit of a dated version of Gosu where I work (something I never thought I'd get to claim on HN...), but I believe that curly braces are perfectly fine to use, and actually required if you have a multi-statement block (essentially starting to look like anonymous functions in Javascript).

Exactly if you want to return just an expression you can avoid them, otherwise if you use statements in the body of the lambda you need curly braces.

OK, thank you both for the explanation. That does sound sane :-).

I'd guess that the point is your sexual orientation is both since it isn't really anyone else's business, but obviously your partners (even if they are super secret partners) will know, making it public?

I think the more recent issue you're referring to is this? http://www.haskell.org/pipermail/libraries/2014-February/022...

Okay, I've read a few of Might's posts, and they're pretty interesting. But it irks me for some reason that nowhere in the posts can I find a date. Am I missing something? Where did you grab this 2003?

From the code. Were I to paranthesise the sentence, "perl as it was written in 2003" would be one clause.