The fact that you think otherwise is precisely the problem. If you don't want to write correct software (which, frankly, isn't any harder than writing broken parsers) you might want to reconsider your career choice.
Unfortunately, sometimes you have to put in some sane limits, because of constraints elsewhere.
To call software that has sane limits to cover 99.9% of usage patterns "broken" is pretty silly.
If you think as a software developer, you never have to make compromises, or make a tough call on what 99.9% of users will do, you're being naive.
Public shaming works to stamp out activities that the shamee knows to be bad/anti-social. I think the case here is well-intentioned.
For a very simpel reason -- you are not implementing a new language, but writing a parser/evaluator for an already existing one. And you shouldn't change the language (as much as all of us have a beef with Javascript).
I think it's pretty sane to suggest that a single statement won't be 4MB in length.