I am sure this topic has been raised before, but I don't seem to be able to find good references to it. The question is that FAQs are generally a semi-active for dealing with issues that come up a lot, so the argument is that if people ask the question so often, then wouldn't it be more beneficial to resolve the issue directly rather than parking it on the FAQ page and getting the users to deal with it? Here is one article that brings up some good points about FAQ pages
While I don't question that FAQ pages exist to help solve a particular problem on websites, I also believe that the format is probably a bit outdated to fit in with a user-friendly experience for the modern day web user.
Is terms of user experience, is there any specific argument for having a FAQ page on a website? Is there a way to encourage the developers to solve the issue asked on the FAQ page, or for the users to get some feedback from the developers other than having their support questions put on the FAQ page? The only example I have seen like this is UserVoice, but this more applicable to a technically or supported oriented site, not a general website.