[zackham]

If your concern is that this is additional unneeded syntax that is just going to result in difficult to understand, overly terse code, my 2 cents is that a conversation among your team to discuss these cases and agree on some standards is a pretty straightforward solution. It's not like today's JS has the Python philosophy of "one obvious way to do it".

I'll throw my hat in with those on the sidelines excited for the language we're stuck writing more of than we may want to, getting another piece of syntax that improves the ergonomics in a lot of little cases. Much like destructuring, much like the optional chaining and null coalescing. It will be nice to avoid the occasional temp variable that isn't useful for readability, or to rearrange expressions that read better applied than composed... but mostly I'm looking forward to how much nicer a pipe operator makes iteratively doing something in the console.