---
title: "Comment by indiainfranotes on \"Day 4: Equality? In JavaScript?!\" | Hashnode"
description: "Nice write-up, Day 4 is where JavaScript stops feeling friendly. The habit that saved me was using === everywhere and treating == as something to read, not writ"
url: "https://hashnode.com/posts/day-4-equality-in-javascript/6ac3b221a0b5c2228a2cbf11/comment/6ac3bb0832f6993fd239f503"
---

[Discussion](https://hashnode.com/posts/day-4-equality-in-javascript/6ac3b221a0b5c2228a2cbf11)

Comment [Day 4: Equality? In JavaScript?!](https://hashnode.com/posts/day-4-equality-in-javascript/6ac3b221a0b5c2228a2cbf11)

[indiainfranotes](https://hashnode.com/@indiainfranotes)

[Oct 5](https://hashnode.com/posts/day-4-equality-in-javascript/6ac3b221a0b5c2228a2cbf11/comment/6ac3bb0832f6993fd239f503)

Nice write-up, Day 4 is where JavaScript stops feeling friendly. The habit that saved me was using === everywhere and treating == as something to read, not write, with one exception some people keep: value == null to catch both null and undefined. NaN !== NaN still surprises people years in, which is why Number.isNaN and Object.is exist. Which comparison result surprised you the most so far?

iin1005ev
