John Gardner

Maybe this is an overly-simplified perspective, but IMHO when built-ins, prototypes and globals are tampered with, it's either because 1. A developer has a damn good reason to, Or, 2....

I second this. Currently, `[mdn.io/Error.prototype.stack](http://mdn.io/Error.prototype.stack)` points to the [German version](https://developer.mozilla.org/de/docs/Web/JavaScript/Reference/Global_Objects/Error/Stack) of the page, despite my browser sending `Accept-Language: en-AU,en-GB;q=0.7,en;q=0.3` as an HTTP header. I also confirmed that DuckDuckGo's _"Language"_ setting...

Bunch of crap I slapped together in Illustrator to demonstrate a concept: Feel free to use or reject it, I'm probably gonna hate it later on anyway. I attached the...

@ptomato It sounds like you're attempting to reference another grammar's rule which doesn't exist. Check the `source.shell` grammar and verify the `repository` object defines the keys `comment` and `case-clause`.

How would this work with built-in modules? E.g., `import("fs")`

I'm talking mainly about subresource integrity. If a checksum is given and a built-in/native module is specified, should it be ignored? Throw an error? Or attempt to verify integrity of...

@domenic What about `"hide source"`?

... again, what's wrong with something short and obvious like `"hide source"`? Honestly, that's all you're really doing. A function's `name` and `length` are technically part of its "implementation", so...

`obfuscate` works, and it's even shorter than my original suggestion: ```js "obfuscate"; "hide source"; ``` Bear in mind that even with stack traces involved, `hide source` is still appropriate because...

@bathos Thanks, I had no idea what the word really meant.