But it's one thing to emphasize a naming convention, and another thing to simply not compile because I want the function be named doSomething() but am forced to name it do_something(). With a naming convention or an included formatter I still can write my style. At least until I'm used to the language's native naming style.
Being forced just annoys me and keeps me from using the language at all. (Because languages differ here extremely.)
This isn't about enforcing how new things are named, this about enforcing using already existing names consistently.
If the documentation says "there is a thing named foobar", but in the code I can see Foobar, FooBar, FOOBAR, FOObar, etc. used interchangeably, that's not gonna help readbility and maintainability.
Being forced just annoys me and keeps me from using the language at all. (Because languages differ here extremely.)