It makes reading easier and writing faster. And no more time wasted on pointless formatting debates.
> And no more time wasted on pointless formatting debates.
There will always be pointless debates: Naming variables, deciding which linters to enable, using reduce() vs. a loop, classes vs functions and so on. This is a cultural problem which occur because you're not focusing enough on the things that actually matter ("is the code correct?"; "can we safely ship this to production?"; "what's the long-term effect of introducing this abstraction/feature/capability?").
I love thinking about code as art, and I have numerous side projects which explores this, but when it comes to shipping real features on a deadline we need to create something which works, not something which evokes a good feeling inside me when reading the code.
I don't know, ask them? We here are on board with using them. ;)
I've met such problematic people. You can't reason with them, it's almost a religion.
But when you sell standardized tooling to your manager plus emphasize how this will reduce internal team friction, you can elegantly eliminate them from the equation.
I did it before and I plan on doing it again. We are here to write code and be productive, not to discuss aesthetics.