I don't blame the initiative behind this website although I'm not too found of it's frontal approach, but there is a lot of elements which needs more facts and less opinions.
@theofidry, you point is actually very valid, but at the same time very difficult to implement in practice.
I personally have a few points on this.
All of the things we express on the website are based upon experience gathered from many different proprietary projects in the industry since the very early days of PHP. The facts gathered from these projects are non-disclosure. Very often such companies don't want to share their findings and studies publicly.
However, it's possible to locate other companies that share their findings or allow a developer to share his or hers experience from a project publicly and such data might be relevant - and yet again often not at all.
We have found that what served this website best was to use a simple and rational approach (with a little bit of provocation, the "frontal approach" as you termed it) against what most can agree is a bad practice.
If we start to present facts from very specific situations we see some problems arise:
Some people will disagree on the basis of "technology" saying that the only reason why OOP or framework X was bad was because they didn't use technology Y.
Some people will disagree on the basis of "the wrong approach argument" saying that the only reason why OOP or framework X was bad was because they didn't use this or that approach.
Other people will disagree simply because they themselves lack the experience to understand the issue at hand.
We find this counter productive and completely unnecessary to prove our very important point.
When we're simply saying - for example - that it is bad to always use a framework most people will use the search engines and look for articles, blog posts, etc., on whether it is good or bad to use a framework.
This way they will do the research themselves!
And a lot of people - natural born programmers at least :) - will also do some test-and-trial for their specific use case, which is so much more important than reading about case A, B, or C that might match or not match.
Also in many public studies several facts are left out which often makes it impossible to really investigate and understand why something was "a wrong way" or "a right way".
The points and ideas we express on the website is based upon heavy experience in the industry, but that's not even important. What's important is that people stop following blindly what is being propagated as being "modern PHP".
Anyone can use a search engine and find this "modern PHP rating" in every corner of the PHP community forums, sites, blog posts, etc. We believe this is bad based upon our experience and we want to express this view.
But we do not want this website to target specific personalities! We believe that would be very wrong. The only thing that matters is the things being said.
Also.. this website is not a scientific research paper.
I am opening this new issue based upon the comment made by @theofidry in the end of this: https://github.com/bitflop/phpthewrongway/issues/27#issuecomment-242772272
@theofidry, you point is actually very valid, but at the same time very difficult to implement in practice.
I personally have a few points on this.
All of the things we express on the website are based upon experience gathered from many different proprietary projects in the industry since the very early days of PHP. The facts gathered from these projects are non-disclosure. Very often such companies don't want to share their findings and studies publicly.
However, it's possible to locate other companies that share their findings or allow a developer to share his or hers experience from a project publicly and such data might be relevant - and yet again often not at all.
We have found that what served this website best was to use a simple and rational approach (with a little bit of provocation, the "frontal approach" as you termed it) against what most can agree is a bad practice.
If we start to present facts from very specific situations we see some problems arise:
We find this counter productive and completely unnecessary to prove our very important point.
When we're simply saying - for example - that it is bad to always use a framework most people will use the search engines and look for articles, blog posts, etc., on whether it is good or bad to use a framework.
This way they will do the research themselves!
And a lot of people - natural born programmers at least :) - will also do some test-and-trial for their specific use case, which is so much more important than reading about case A, B, or C that might match or not match.
Also in many public studies several facts are left out which often makes it impossible to really investigate and understand why something was "a wrong way" or "a right way".
The points and ideas we express on the website is based upon heavy experience in the industry, but that's not even important. What's important is that people stop following blindly what is being propagated as being "modern PHP".
Anyone can use a search engine and find this "modern PHP rating" in every corner of the PHP community forums, sites, blog posts, etc. We believe this is bad based upon our experience and we want to express this view.
But we do not want this website to target specific personalities! We believe that would be very wrong. The only thing that matters is the things being said.
Also.. this website is not a scientific research paper.