6 ms·
> This topic (I do not know why) raises some serious emotion-based responses on coders. I saw the title on HN, and was like "uhhh, no shit, why is this here?".
by flomo 12y ago
> This topic (I do not know why) raises some serious emotion-based responses on coders.
I saw the title on HN, and was like "uhhh, no shit, why is this here?". Then surprisingly, it all of a sudden it has 80 points and almost 50 comments debating the details. I don't think there's any actually real debate on how Java actually works, this must be a purely linguistic. Or as you say, "emotional".
SQL NULLs, on the other hand, is a real philosophical war. One which the wrong size is clearly wrong and need to be crushed into ashes underneath our boots. We are not debating jargon, we are defining databases which could certainly outlive our sons and daughters!!!! .. Ok, sorry. But I just don't think it's good comparison with students who just don't really get Java. Database design is largely a matter of opinion, Java method calls are not.
- probably_wrong 12y agoIt is definitely emotional for me: I remember reading yet another of these "java is not pass by reference" posts, and the title stuck for some reason. So next time I wrote a Java function (long afterwards), I modified a list received as an argument inside a function, and could not understand why my original list was modified. I honestly feel that these posts titles are just trying to pull my leg. "Java passes everything by value!" "Really? And which value is being passed?" "The reference, of course!".
- lucio 12y agoI'm on the same page as you, that's why I'm getting the downvotes.
- jjnoakes 12y agoSo instead of programming based on vague recollections of blog titles, you should strive to understand the language you are writing in, so that you don't make those mistakes. Reading the content of the articles, doing some research, and actually understanding what is happening in the language are all good steps to consider taking.