That's because it's an anti-pattern. This is not a valid use case.
An interpreter already executes code, so you don't need to wrap it in a function. Remove the function, and you've got the same output.
If you need to repeat execution, you should define a function with a descriptive name.
In this case, the result will always be the same, and the whole function can be replaced with its output to save on execution time.
An IIFE is still common. It's often used in browser
content extensions or snippets loaded from providers (analytics, ads, ...), because the browser's scope is shared by all active snippets, so we limit the scope.
That's because it's an anti-pattern. This is not a valid use case.
An IIFE is still common. It's often used in browser
content extensions or snippets loaded from providers (analytics, ads, ...), because the browser's scope is shared by all active snippets, so we limit the scope.
Well, there's that, too. 😅