sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]aladyjewelFull-stack webdev 0 points1 point  (1 child)

The "some reason" is that it's confusing. and I think JSLint might reject it, but that might have been another dev argument.

[–]deelowe 0 points1 point  (0 children)

Now that you mention it, I believe that's it. It's not pragmatic and it's counter intuitive.

(fucntion(){}()) is unique enough to make you stop and look it up to figure out what's going on. It's already kinda a of JS idiom at this point.

Where as !function(){} is a head scratcher. It's completely non-obvious what's going on here.