Any syntax could be taken to the extreme.

In small doses, destructuring can greatly improve readability.

// handling dimensions
let { width, height } = canvas;

// handling vector arrays
let [ x, y, z ] = position();

// swapping variables
[ x, y ] = [ y, x ];

More on reddit.com

This blog post is just looking to find problems that don't really exist. It's fairly obvious that you can't destruct an undefined value, just like you can't do pretty much any other stuff with it, like accessing its members. It also strikes me as odd to do the destructuring as an argument, just pass user.email instead of user to the function. City isn't undefined, it exists and has the value null. So I'd rightfully expect city to become null when it's destructured. More on reddit.com

I don't find this particularly useful, you're casting new variable names rather than accessing an existing object.

Is the following not easier to read and much nicer to maintain? References original object for manipulation and promotes nice code, has the same outcome with the same amount of code?

for (const country of countries) {
    console.log(`Name ${country.name}, Population ${country.population}`); 
}

More on reddit.com

Honestly destructuring is one of my favourite things about the new spec when considering how frequently I use it. It really is very useful for keeping code concise and easy to reason about. More on reddit.com