I think we need to try and filter out not just bias, but also oddities that don't fit with the consensus of what we know, and accounts where we know the technical details are plain wrong.
So the opening Reddit post just doesn't match what the consensus now seems to be, and in detail it appears to just be down to an unoptimised PC port, given it was from GDC perhaps not too surprising.
On turbosquid's post he simply doesn't understand PS VR frame rate: he thinks the HMD is receiving 60 or 70 fps in some cases, whereas in reality it is receiving either 90 (native + repro) or 120 (native+ repro, 60 fps = repro) from the breakout box. Given his basic misconception we can't trust what he is saying (bias). He might be seeing stuttering if the underlying game is not delivering a consistent 60fps. Overall though not a bad summary.
The Gizmag comments have been discussed before, and I think they needed to try the best motion controller demo available (London Heist) before making such damming comments. Also they are obviously ignorant of the technologies involved (recycling a pair of Wiimote-like controllers). I think what they experienced was likely due to developer implementation (and possibly environmental lighting), however they may also be seeing orientation drift. The PS move should be as accurate positionally as Oculus Touch given the technology both are using. However one issue with the move is that while it shouldn't drift positionally, orientation drift is definitely possible and may even be likely. Most observations around the London Heist are very positive as to the accuracy of the controllers, however I've noticed this isn't the case so much with other games. I think the Jury is still definitely out on this one.
