It looks like it’s just assigning the scope variable
mtotrue(alsofalsein them=!1case.It’s minified code and
m=!0is fewer characters thanm=true.Well I hate that. Is there a reason
m=1wouldn’t be the same thing asm=!0?Types are dynamic so I think the ! operator converts int to bool in JS
1 is truthy, but not the exact same thing as true, and the distinction can be important.
1 != true, 1 is an int, true is a boolean
deleted by creator
!0is shorter thantrue,!1is shorter thanfalse. You are looking at minified javascript.It’s not code anyone is supposed to read or work with, this is the result of minifying it to be as short as possible. And from a quick glance what’s happening is that a variable is set to correspond with whether the cursor is currently over a certain element. Not sure what’s funny about this?
A blurry chunk of screenshot that someone bled on, that’s what.
You can go one step further and use the Bang-Bang operator:
!!mTo be read as “Bang! Bang! You’re a boolean now!”
I might be in the minority but I prefer to do it like this:
Boolean(m).It’s the same thing but less cool. On the flip side it’s easier to read when you have a line full of operators.
Yep, that’s a much better way! It’s like the “goes down to” operator - a neat trick you should never use :)
while (i --> 0) { ... }
Right now … You’re looking at my comment
