it sort of remains amazing that you are convinced that this casual benchmark which has already had two severe problems exposed and doesn't show its approach is not the problem, but rather that it's this library that is in heavy use and that everyone else seems to not have these problems with
Well, I think the author's point is that the conventional hive mind wisdom in the community that uses this product has been that DOM manipulation causes performance problems and the framework is wicked fast and not a source of performance issues... which may lead naive or new developers to never both to consider it as a potential source of problems. This very clearly illustrates it may be possible that you shouldn't always disregard the framework as a potential source of problems...
