A question about the future coding style guide

http://cs.sensiolabs.org
https://github.com/bobsta63/netbeans-psr-formatting
Probably there are more developments like these.

Automation on code styling would be nice, then more time and commits would be spent on creative subjects.

> nor is there any meaning in tools "supporting" it - that's just a fallacy.

Sorry, my English is just broken.

I meant tools like:
* PHP Coding Standards Fixer http://cs.sensiolabs.org
* PhpStorm https://www.jetbrains.com/phpstorm/
* Nitpick CI https://nitpick-ci.com/

What can I say them?

Nah, your English is OK. I assumed by "tools" you meant other frameworks and libraries. But IDE functionalities as arguments in this context is another common fallacy and sadly, I've even seen it in PHP RFCs.

That's like rejecting a new feature because an IDE doesn't support auto-completion for it - of course it doesn't support it if it doesn't exist yet. Such tools are written to help you and are driven by frameworks', libraries' and language's features, not the other way around.

These tools had support for other "standards" before PSR-2 existed, somebody wrote the patches or plugins for it afterwards; the same will happen for every popular styleguide.