CanadaMark Offline Upload & Sell: Off
|
prosumerhacks wrote:
While I agree with being logical, tearing into someone's description of an issue they noticed and declaring it's not statistically supported, isn't the best approach. The person who made this particular statement seems to merely pointing to a discussion while furnishing some "user" data. I agree that this lens is not professionally reviewed but how many professional reviews in the recent history has been accurate until users clamored for quick redressal for problems which were first reported like these?
I hardly "tore into" his statement haha, that is quite the exaggeration. I don't think anyone on here is that sensitive. The person made a blanket statement that it is an unresolved issue with the 300/4 VR based on the way it was worded, which is all we have to go on. I strongly disagree with making blanket statements based on little to no data, so I replied to his post. I'm sorry if you somehow took offense to it.
If it turns out to be a legitimate issue, so be it, Nikon will recall and it'll be delayed by a couple months, no biggie. Could also be a simple firmware/communication issue, rather than an actual build/design issue. Time will tell. My only point is it's FAR too early to be coming to conclusions about anything, even though there could very well end up being a recall.
|