Thoughts
Hot take: from a language design standpoint, it's an anti-pattern that `{} !== {}`. The end-user-programmer should have to create and
attach unique id properties if they need to be able to tell two objects apart later.
I don't know, the alternative is weird too.
The alternative is that it's a language-implementation-detail how many copies of your object there are in memory, and if the language wants to collapse two objects together, then it can. But that's obviously wrong because the same data in two different variables shouldn't be collapsed into the same memory region.
Like look at how Python handles `is` with numbers. Something's obviously wrong there. Is it going too far to say that `is` shouldn't work with numbers at all?