This website contains age-restricted materials including nudity and explicit depictions of sexual activity.
By entering, you affirm that you are at least 18 years of age or the age of majority in the jurisdiction you are accessing the website from and you consent to viewing sexually explicit content.
Ah ha, I found a JS dev lmfao
Normal languages: “does this equal that?”
JS: “does this REALLY equal that, or just ‘equal’ that?”
JS comparing a string and some random number: “ah, close enough probably”
Beats having explicit null checks everywhere.
As opposed to null and undefined?
No one checks those values explicitly.
if (str)checks if it’s not null, undefined, or empty string.Optional chaining like
if (arr?.length)checks if list is undefined, null, or empty array.Falsy and truthy comparators seem fucky in the beginning when coming from a strongly typed language. But they’re very convenient when used properly.
Monads exist, optional chaining has been around for ages, and implicit bool casts, too.
As you said, no one checks those values explicitly.