This is confirmed to be bullshit. That sensationalism... sad HN. Not even sure how people can believe something so stupid so fast and jump on the hate train.
"This is confirmed to be bullshit." - Where? For a real confirmation I always use the Wikipedia check: Reliable third party. Sorry, but Blizzard is not a reliable source for an conformation in this case.
If blizzards confirmation isnt enough then who are you even going to believe? I can't think of anyone whos actually more reliable blizzard in this case. You prefer to believe random angry people on the internet who got banned for cheating?
I completely believe Blizzard, but are you seriously suggesting that any time anyone is critical of that company, if the company says "not true" they must be correct?
Im simply saying that blizzard wouldnt lie when they say that playing on linux will not get you banned. I did say "in this case" specifically, because im not going to claim that they never ever would lie.
It does what it's intended to do. Use the methods you are supposed to use. You're just arguing for the sake of arguing now, or you just don't know what you are talking about at all.
If you are trying to hire an "expert" and ask him questions like that, you are doing it really wrong, unless you are trying to scare him away. If anything you want to actually talk to him about what he has done, about the languages, his thoughts and passion in the subject... not ask him first programming classes in college questions.
However if you are trying to hire some kind of junior-like engineer who has never had a job before, i can see why questions like this could be asked, but i still dont think it's the best way to gather knowledge about the person you are interviewings level of expertise.
I think these could be weeder questions for people you know little about.
If you have an applicant who has a github full of great code or experience working for a good software company you can probably skip this.
However if you get a candidate without much on paper but who insists they are a Java expert but doesn't know what the extends keyword does then there is something wrong somewhere.
The problem with asking for definitions for words though is that I personally often forget exactly what these are if I ever learned the correct term in the first place.
For example I knew how to override methods and the differences between the type system in PHP and the one in Java long before I knew what polymorphism or "dynamic typing" meant.
So ask the programmer to program or debug something, give him a decent IDE and access to Google. Don't ask him to answer trivia. 'Can you fix this simple 10 line function' is much less insulting.
It is a huge turn off for a lot of people and indicates that the interviewer is either too lazy to make the question interesting, or not technical enough to generate an actual good question. Either way it is a red flag.