I guess Safari on desktop isn't considered a mainstream browser vendor anymore? Or do they regret implementing it also?
The appeal of the explicit syntax makes sense, but the argument that proper tail calls are hard to identify/create seems silly to me. Devs have any number of ways to create memory leaks which have even harder to diagnose problems than the stack overflow of an improper tail call. The stack without tail calls overflows quite quickly unlike memory leaks which only a minority of users can experience on certain code.
But I find the need for step debugging to catch and unroll a virtual equivalent to tail calls a better argument given that this is for a sandbox for adversarial code with strong incentives to obscure bad behavior.
It's extremely obvious to think about tail calls when you know you are supposed to be thinking about tail calls. The life cycle of JS Code doesn't usually make anything obvious to people who inject the last edge conditions in a function.
I think they are not shipping that anymore.