== is a heathen with no rightful place except equality to null. All praise ===
Sorry, 0 == '\t'? What?
that’s not “t”, it’s “\t” which is just a tab. There’s also “\n” for newline.
If " " wasn’t equal to 0, it wouldn’t make sense, but since a string containing a space equals 0, you’d expect the same to apply to a string containing a tab or a newline. (or at least I’d expect that)
It’s a slash-t in the comment. Maybe kbin has different rendering rules for comments?
Oh, in that case I replied to @MinekPo1 with my answer to that. BTW can you see the slash in: \t and "\t".
yeah but why is a single character string containing a tab equal to zero ???
The == operator in JS will try to cast the things being compared and do all kinds of ‘smart’ assumptions about what equality means. This is why everyone uses === instead…
Are people really not using the strict equality operator?
It’s still pretty bad that the normal equality operator is as bad as it is.
If you’re provided a tool that solves a problem, I don’t really get ignoring that and continuing to focus on that solved problem as if it weren’t solved because you think all the tools should solve it on principle
That’s a little bit like saying, “I don’t understand why people continue to complain about the landmine sitting right there on the ground. We’ve painted it red so you can easily walk around it, so how has the problem not been solved?”
“The trinity makes as much sense as Javascript” is a vulgar condemnation of Christian dogma.
Fuck this language with a pineapple
