In the micro, this is definitely a useful crutch for using badly-written/badly-behaved code.

(In the example, it usefully provides a way to maintain sanity when `app1.rb` and `app2.rb` both define a global constant named `PORT`)

However, I'm not sure how much existing code is defining stuff in such a poorly considered way. (I don't mean that rhetorically. Maybe it's more pervasive than I think)

Furthermore, would adding this feature to the language actually encourage such bad behavior? (Would it even be "bad" behavior at that point?)

So I'm kind of leaning toward "I can see how this would be useful, but I don't want the language to condone such a bad practice."