[petercooper]

As the editor of Ruby Inside, I can confirm we (or me, as author of the piece) were not involved in any conspiracy or malicious intent against Hpricot. Heck, Why even wrote the foreword for my book :)

Further, the benchmarks we republished were not by us, but just a screenshot of benchmarks shared by the creator of Nokogiri.

[thismat]

This bothers me honestly, why would you accept benchmark screenshots from someone that made claims against another persons code?

Was this an interview or something? Was _why alerted to this as a chance to refute the claim by providing his own benchmarks? Could the data even be validated and not easily doctored?

[petercooper]

The benchmarks were from what was designed to be a fair test. It might not have worked out that way, but that was the intention of the creator nonetheless. I stuck a massive disclaimer on my link to those benchmarks and let people at it (since NO benchmarks are EVER undisputed - biggest lesson I've learned). The post is at http://www.rubyinside.com/ruby-xml-performance-benchmarks-16... if you want to see how it was portrayed.

If everyone had to bother validating all the third party bits and pieces that get referenced on blogs, no-one would blog. Blogging is a "hey, check this out, I ain't saying it's true, but you might find it interesting" type of affair - it's not the New York Times (which is why regular journalism is foundering; it's expensive to fact check everything and, heck, it's a Ruby blog, not a trusted source of journalism).

[bunnny]

Yeah, it sounds like you were really trying to be thoughtful, gracious, and evenhanded in your comparisons:

Nokogiri: A Faster, Better HTML and XML Parser for Ruby (than Hpricot) http://www.rubyinside.com/nokogiri-ruby-html-parser-and-xml-...

[thismat]

I figured it had to be something of that nature, and indeed, the disclaimer is clear about the data presented.

Upvoted for the explanation, thanks.