Probably how many people clicked on what url. There are probably some information about those, the more trivial would be from where in the world they are and how they got there (following a link, being redirected or having entered it manually)

More complicated stats would include estimated age, gender etc, if available

That looks cool

American police: they think they know what the law is.

If you have the need to nest 5 levels of for-loops, I suggest taking a step back and rethinking your approach, my friend.

Even if that other approach is just refactoring it into separate methods.

Maybe I’m not comfortable anywhere then …

Not a JavaScript dev here, but I work with it. Doesn’t “==” do type coercion, though? Isn’t that why “===” exists?

As far as I know the operators “>=” and “<=” are implemented as the negation of “<” and “>” respectively. Why: because when you are working with sticky ordered sets, like natural numbers, those operators work.

Thus “0<=0” -> “!(0>0)” -> “!(false)” -> “true”

Correct me if my thinking is wrong though.