Programmer Humor

20039 readers

2927 users here now

Welcome to Programmer Humor!

This is a place where you can post jokes, memes, humor, etc. related to programming!

For sharing awful code theres also Programming Horror.

Rules

Keep content in english
No advertisements
Posts must be related to programming or programmer topics

founded 2 years ago

MODERATORS

[email protected]

1436

"Works for me" (lemmy.sdf.org)

submitted 1 week ago by [email protected] to c/[email protected]

83 comments fedilink hide all child comments

you are viewing a single comment's thread
view the rest of the comments

[–] BroBot9000 15 points 1 week ago (12 children)

I’m going to have to go down the rabbit hole of making my own website soon. Just curious but would there be an easy way to show a pop up just to people using chrome?

No reason in particular… 😏

[–] RedStrider 18 points 1 week ago (1 children)

lol i did something like what i assume your goal is on my neocities when i detect !!window.chrome === true

[–] [email protected] 7 points 1 week ago (2 children)

Why the double negation?

[–] rektdeckard 12 points 1 week ago (1 children)

It's a handy way to convert any value to a Boolean. If window.chrome is defined and done non-empty value, double negation turns it into just true.

[–] [email protected] 6 points 1 week ago (2 children)

I've been wondering why not window.chrome == true or Boolean(window.chrome), but it turns out that the former doesn't work and that == has essentially no use unless you remember some completely arbitrary rules, and that JS developers would complain that the latter is too long given the fact that I've seen javascript code using !0 for true and !1 for false, instead of just true and false because they can save 2 to 3 characters that way.

[–] marcos 6 points 1 week ago

== has essentially no use unless you remember some completely arbitrary rules

If you make sure the types match, like by explicitly converting things on the same line on that example, then you can use it just like if it was ===.

In fact, there are people that defend that if your code behaves differently when you switch those two operators, your code is wrong. (Personally, I defend that JS it a pile of dogshit, and you should avoid going to dig there.)

[–] [email protected] 5 points 1 week ago (1 children)

I've never seen the !0 and !1, it is dumb and indicates either young or terrible devs.

Boolean(window.chrome) is the best, !!window.chrome is good, no need to test if it's equal to true if you make it a boolean beforehand.

[–] RedStrider 1 points 4 days ago

i just added the === true for clarity

[–] [email protected] 5 points 1 week ago

JS "idiomatic" way to cast to boolean. But could just be written as !window.chrome instead.

load more comments (10 replies)