zlacker

They were warned. I don't see how this can be characterized as anything but sloppy.

>>dizlex+(OP)
You can call anything, anytime, anywhere without restrictions or protection.

Imagine these dozens of people, working at Meta.

They sit at the table, they agree to call eval() and not think "what could go wrong"

>>rvnx+Rm
Eval has been known to be super dangerous since before the internet grew up and went mainstream. It is so dangerous that to deploy stuff containing it should come with a large flashing warning whenever you run it.

>>jacque+JG
hmm isn't eval is used in figurative-sense here eh?

maybe you should get some sleep

>>jacque+JG
Half of web map solutions rely on workers, which can't be easily loaded from 3rd party origins, so are loaded as blobs. loading worker from blob is effectively an eval.

>>febusr+Er1
The client sort of exists to have code injected into it though?

>>__alex+gy1
If you want to describe text mark-up as programming, then yes. But most people do not do that.

>>sysgue+1p1
No, their whole point is that what they are doing is the literal equivalent of calling eval. Whether that actually uses the word 'eval' or a function called 'eval' is besides the point.