miniblog.

I'm a huge fan of Swift's 'Error Handling Rationale' design document: https://github.com/swiftlang/swift/blob/9315673c003875158852579bd1f33480cdec5461/docs/ErrorHandlingRationale.md#fundamentals It carefully defines terminology and compares with other languages, so you can understand Swift's position and preference in the design space.

It's good to see websites acknowledging the grim irony that you need cookies to remember users' cookie preference. I'm surprised that there isn't a microformat specification for this yet. If one browser enabled users to blanket hide all of these I think others would follow.

I don't understand the preference in ML family to use currying so enthusiastically. Eg in the signature of a sort function, I prefer (a,a)->Ord as the comparator function signature, vs a->a->Ord. It's easier to distinguish inputs and outputs. Are there upsides I'm missing?