Deep equal is not the `==` operator in JavaScript

The == in ReScript is not equivalent to the == in JavaScript after compilation
In other words, Caml_obj.caml_equal is not equal to == in js
Running into this today with my team. Its possible to do shallow and deep equality between polymorphic variants, for example, where the js representation is variable, and referential control is not clear, desired, (or possible), causing #Y(3) === #Y(3) to be false.
Whats worse is that Js developers have, in the recent past anyways, been taught to use === everywhere. So if they don't have any particular intent they will very often use === .
I have made some noise before but it strikes me that strict equality should be removed as an operator and moved to a Js specific location that clearly explains whats going on and prevents its use broadly in the language?
see also #503