Yeah, this is always an interesting question. You want to introduce new syntax and features because you want the team (as well as the codebase) to mature and learn, as well as the potential benefits of the code change itself.

But you also don’t want to be making willy-nilly changes with extreme edge features that just antagonise or alienate the team.

It ultimately comes down to knowing the team. Some teams are excited learners, eagerly leaping on new features, others are JavaScript users only under protest and resist change. Only you know your team and what works for you.

In this particular case, though, I think the overhead is surprisingly minimal (given a pre-existing build setup, etc) and the syntax change is small and easily comprehensible. As I said in the article, a good bang for buck.d