Hacker News Reader

HNHacker News

Top New Best Ask Show Jobs

Comment by nrjdhsbsid | Hacker News Reader

Parent Full thread

nrjdhsbsid·

Hahahaha

Edit: I'm a Java guy too, don't get why some people get so butthurt over things :)

At least it's not JavaScript with infinity,null,undefined, and NaN. Oh and null!=null which is hilarious

View on HN

You mean NaN != NaN. null == null is true, and null != null is false.

NaN != NaN is surprising, but is not unique to JavaScript. As far as I know, this is the case in every language, and is mandated by the IEEE 754 specification.

However, it does come up in JavaScript more often than other places, since NaN is really easy to get (+{} => NaN, 1 - '' => NaN, etc, etc).

LOL yeah.. don't get me started about JS :D.

I more of a C++ guy, but I like Java very much and have used it extensively in the past. I personally like a good C/C++ joke and can't understand why the Java devs are so serious. Apparently nobody is allowed to joke about Java, it's serious business :D

For what it's worth, you should _always_ be using triple-equals in Javascript unless you have an overwhelmingly good reason not to. Many of the weird Javascript-isms people like to complain about are due to surprising type coercions, which don't happen with triple-equals (which behaves as you would expect- value equality without type coercion for primitive types and reference equality otherwise.)

For someone who uses a more than one language on a regular basis, triple equals is an annoying break with convention. It shouldn't be that easy to make a mistake by simply missing an extra character. This is one of many reasons I've taken to using TypeScript for all of my web frontend projects.

However you still run into the same problems with > , < , <= , and =>. So you need to really really understand the corner cases (same as with C++).

In SQL, 'NULL <> NULL' is true as well, you have to use 'NULL IS NULL' instead, so the concept has a long and somewhat respectable pedigree...

Reply on news.ycombinator.com