It does, maybe the post or comment got deleted.
Actually, no. The post is still up and the comment too. So maybe it's just in case it gets deleted.
Limitless_screaming
joined 1 year ago
== but for JavaScript. What you don't understand is the == of JavaScript.
I'll try out Privacy Badger. I never got an ad on Firefox except for this one.
There's a loud ad for "Duolingo super" that has a high chance of showing up after every lesson. Also using Firefox with Ublock installed, and it's still here.
The site itself; Facebook, Reddit, or Twitter sends you to a subdomain that then redirects you to the link you clicked. Sometimes used to check the url and warn you if it's malicious or if it's linking to another website, but it's usually used for tracking as well.
My bad. I just edited it. "\t" \t It's displaying correctly on Lemmy.world. So it seems like another Kbin only issue.
Yes, it would. Just like a string of spaces " " == 0, but it isn't that bad; === is Javascript's version of == in other languages, and, thus, you should be using it if you don't want that wonkiness.
== is just for convenience, like when you want to make sure that the user didn't leave the form empty and the button shouldn't be greyed out, and other UI stuff. Without these kinds of features JS wouldn't be used in so many toolkits.
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)
Oh, in that case I replied to @MinekPo1 with my answer to that. BTW can you see the slash in: \t and "\t".
That would be weird if a string containing a space wasn't equal to 0 " " == 0, but that's not the case in JS. If you think that "" and " " being equal to 0 is weird then I agree, but since they are, you should expect "\t" and "\n" to equal 0 too.
view more: next ›
So the architecture just needed more data to generate useful answers. I don't think that was an accident.