| > Attention to detail leads to code quality. I agree. But the PSR's approach things the wrong way IMO. The style related PSR's should be exactly two rules: 1. Choose an existing/define a formatting style for the project. 2. Ensure the style is enforced, ideally using a code style formatting tool like phpcs, your IDE, etc Thats it. Claiming that a project isnt up to scratch because it doesnt conform to an abritrary style that was created literally by what was most common in the member projects at the time, is frankly ridiculous. Their subsequent decisions show a frankly laughable approach to development. Psr-whatever that defines a logging interface. Every man and his dog uses integer levels, usually the syslog 0-7 range. This makes it extremely simple to ignore/filter out logs above a given priority. What do they decide to do? Fuck it, make the defined log levels strings. Why? Because an existing project happened to already use integers that didnt adhere to syslog, and they didn't want to deal with it. So fuck it, lets have a shittier, less sensible "standard" just so fucking monolog can keep using 400 to mean error or whatver it is. Readability is good, standardisation is good. The latter should be a project level decision, and honestly ive never seen anyone who's picked a standard - any standard - that meant readability was a problem. |