I think we all have but that doesn't change that this is almost exclusively a js specific interview question with a very js'y solution to the point of hammering

I think we all have but that doesn't change that this is almost exclusively a js specific interview question with a very js'y solution to the point of hammering in a imagined "js land" api. I am not against testing deeper language understanding for a job that requires it but the layers of contrivances to make it "not only js" rightfully rubs non-js devs the wrong way. This comes from someone who loves them some js. The AI ick at the end makes what would have been mildly interesting, incoherent and uninteresting.