I don't see why they couldn't just name it global. There's the "let's not conflict"-argument, and "let's fight around with existing types".
But in all honesty... there's not much you can "assume" about the global object anyways, you will still have to check if (global.feature) for most features if you're building a cross-platform lib, and I'm not sure how globalThis would help with that.
"Attempts were made to ship under the name global, but it turns out that this does, in fact, break some existing websites." per the spec github.com/tc39/proposal-global
Thank you for sharing! ✌️
We're a place where coders share, stay up-to-date and grow their careers.
We strive for transparency and don't collect excess data.