Valid UTF16 is already being sporadically enforced. People who hack JS to store arbitrary data in strings are already fighting a loosing battle, and I see no p

Valid UTF16 is already being sporadically enforced. People who hack JS to store arbitrary data in strings are already fighting a loosing battle, and I see no point to help them. But my point is that we have moved from the JS as a scripting language which did not allow for arbitrary binary data, to one which did without much though over that. Half of existing problems with zero click, zero days, and zero browse exploits running in the wild, and Chrome becoming the ActiveX 2.0 is that. There is really no reason for a web browser to do computing on the web, and thus no need for binary manipulations in Javascript on the web. I'm not saying to axe it from JS, but JS may limit the the browser use case by a limited set of JS standard.