So true. Even when Dr. Pabst has made some controversial claims, they still had enough evidence behind them that you could debate them from either side. However some of the other writers (Patrick Schmid and Frank Völkel specifically come to mind) have a bad habbit of making some completely unsupportable claims or giving some wild narrow-minded opinions, and doing so fairly regularly. It has gotten to the point where unless it has Dr. Thomas Pabst's name on it, I completely ignore everything but the benchmarks themselves.
What gets me though is just how hard would it be to hire (or 'promote') a single editor to review articles before they're published? Heck, I bet there are plenty of people here who would be willing to do it for free just to get their name on something to put down on a resume. (Or even just for the fun of it.)
It might add a whole hour to the publishing process, and yet it would raise the bar of professionalism of the site back up to good standards.
I mean I can understand some of the typos and bad grammar being due to language translation or English not being everyone's primary language. And I have no problems with that. I mean most people on the planet don't even speak English as a primary language, if at all. I know that the <i>only</i> second verbal language (I won't count computer programming languages) that I know, I can still only barely speak or write as I only spent a year in high school to learn it. So I could hardly judge others for not having perfect skill in their second language.
However, I would find it very difficult to believe that making a claim that an IDE hard drive outperforms a SCSI drive is due to just a language mistranslation. And that's the kind of stuff that makes me hesitate on even reading THG's articles some times.
But hey, it isn't my company, so it isn't my job to fix it. If Dr. Pabst wants his good name being drug through the mud by some of his employees, that's his choice. And I'll just continue to complain every so often in the hopes that someone on high finally listens.
<pre><font color=green>//error-proof coding</font color=green>
<font color=blue>void</font color=blue> main(){<font color=blue>return</font color=blue>;}</pre><p>