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!
-
Show this thread
-
The article I'm subtweeting did NOT make this mistake, and was up-front about this limitation. But that article caused internet fights, and the commenters in THOSE made that mistake. (the other big mistake people made was "commenting without reading the essay.")
1 reply 0 retweets 31 likesShow this thread -
Replying to @hillelogram
What % of commenters do you think read posts before commenting? From reading comments threads that are mis-titled, where everyone is commenting on something unrelated to the actual post, I think it's under 1%. I wouldn't be shocked if it's under 0.1%, but I suspect it's over.
2 replies 0 retweets 5 likes -
Replying to @danluu @hillelogram
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.
1 reply 0 retweets 0 likes -
Replying to @danluu @hillelogram
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.
2 replies 0 retweets 2 likes -
Replying to @hillelogram @skamille
It usually won't be phrased with an XOR and will instead be phrased like "I'm looking for a car that has 4 doors or is a hatchback, but not both"
1 reply 0 retweets 0 likes
That's a bad example because it would probably get some matching answers since, if you start naming cars at random, you'll name some 4d non-hatchbacks. But if the question can't be trivially answered by ignoring all of the criteria, then the asker will probably not get an answer.
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.