When talking about static types you can't just take the union of all the best features in all type systems. Like if one gives you A but not B and another B but not A, you can't say static typing gives you A and B. You're going to write your code in just one of them!
By "read" I mean "at least skimmed to the bottom", if we're talking about people who really read the thing in detail, then I'd guess well under 0.1%. I've been thinking about this in the context of content people have a hard time with.
-
-
Like, if you read an ask.metafilter question with an AND, you the questioner is probably screwed. 95%-100% of the commenters will drop half of the question and give an answer that's irrelevant. With XOR there's no chance, 100% of answers will be irrelevant virtually all the time.
-
I'm thinking of how
@skamille occasionally pokes the code review hornets' nest by asking a very specific, nuanced question about the overhead of code review, which people inevitably read as "CODE REVIEW: GOOD/BAD???" What's an example XOR question? - 2 more replies
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.