Re: Why globalThis instead of something intuitive like globalObject, systemGlobal, or globalEntity?

If you look in the proposal's repo, they explain the rationale behind the identifier: https://github.com/tc39/proposal-global/ Here's a short summary: `globalThis` is the same value you get from evaluating `this` in the global scope of a sloppy mode script. This is subtly different than a "global

Re: Why globalThis instead of something intuitive like globalObject, systemGlobal, or globalEntity?

This question is more appropriate for the proposal repo, in which a very lengthy naming document will hopefully answer all of your questions: https://github.com/tc39/proposal-global/blob/master/NAMING.md Please address all further comments or replies on this topic to the proposal repo. Thanks!

Why globalThis instead of something intuitive like globalObject, systemGlobal, or globalEntity?

I know it may be too late for this, but I imagine `globalThis` can bring confusion to beginners, especially ESL beginners. Things like `globalObject`, `systemGlobal`, or `globalEntity` would've been more intuitive; they make sense in plain English. Well anyways, have a good weekend! - Joe