I think that his digs about user experience are based on UI toolkits and following all the Apple interface rules and conventions. His example at the end of the

I think that his digs about user experience are based on UI toolkits and following all the Apple interface rules and conventions. His example at the end of the post is the desktop version of Amazon Kindle (bad, because it uses the QT toolkit and its buttons don't line up in an Apple-approved way) versus the iPhone version of Kindle (good because it's "a native iPhone app, written in Cocoa Touch"). It's a pretty standard line: Apple does it better by scrupulously maintaining identity of interface design and conventions; Linux or Android or Windows is less good because there's so much more variety (visually and in terms of what buttons do what). (Please note: I'm describing a common argument, not taking sides on it one way or another.) So in that sense, he's not really talking about programming languages so much as UI toolkits and I suppose the conventions that go with them. If there were a way to turn Haskell code into a perfectly Cocoa UI, he might very well like it fine. Though, actually, in my experience, he usually finds a way to side with Apple no matter what else is the case...