I think most of the problems with globals can be solved at a language level. Immutable references to globals are practically never a problem, so if your languag

I think most of the problems with globals can be solved at a language level. Immutable references to globals are practically never a problem, so if your language forced you to explicitly mutably borrow a reference to a global variable you force the programmer to think about every instance of code where they are modifying the global. This also enables tooling to for example syntax highlight these things differently. An immutable global looks like any other variable, but a mutable global is bold red. You bet your ass that people will think about whether they really need it mutable in that case, and they'll know everywhere it's made mutable and therefore error prone. Again this comes back to shepherding. Globals in Rust aren't the same as globals in C++ because the languages shepherd you differently.