I mean, the idea is great, but the small amount of parameters supported makes it pretty much useless. Indentation character and size, line termination, ... and that's all. I would need a hundred of these (like clang-format, yapf, etc have) to switch to EditorConfig. Unfortunately, looking at the commit log frequency, I doubt EditorConfig will ever have more than the 10 or so parameters that it already have.
No, it doesn't solve all the things. My experience is that it addresses one specific annoyance - team members checking in changes with varying line endings and spaces/tabs settings - and makes it a thing of the past.
For solving that one thing, I like it a lot.
If this is really a hard problem for a team then it's down to the people not the tools.
There is in my experience no "bother to use them" part, it happens automatically when a file is saved.
Even better, "the right plugins" might be none at all. Some IDEs come with editorconfig support out of the box: https://sorokoletov.com/2016/11/28/editorconfig-in-visualstu...
In short, if you have these specific problems, life really is easier with editorconfig.
It's only meant to automatically configure your editor to use the defined tab/space newline preferences per file type.
that's it.