Therefore, your visitors will be better served by, instead of having them download a PDF file, if they can view it directly in their browser. Just like with audio or video viewers, a document viewer simply resides inside the browser frame and the visitor can view the document without leaving the browser. Because the document is downloaded by the browser cache, it doesn't litter the downloads directory, and the browser will manage the cache'd copy of the document A much better user experience is had by all. Especially if this can be accomplished with pure JavaScript and not a browser plugin.
What I've done in the past is use the Google Docs Viewer to provide an embedded Viewer to my visitors. While that's a powerful viewer application that can handle dozens of file formats, it has two limitations: First, the visitor has to be logged into their Google Account (if they have one). Second, there is some kind of bandwidth cap and the visitor might see an error message rather than the document.
I've decided to abandon Google Docs Viewer because of those reasons. I'd learned that PDF.js, a new component in Mozilla that handles PDF viewing, can be used standalone, but it's pretty complex. Fortunately a team of people have created the Viewer.js project, which uses PDF.js and a couple other libraries to provide a document viewer any website author can use, and supports a couple additional document formats to boot. It's not quite as good as Google Docs Viewer, but it'll improve as the Mozilla team improves PDF.js.
Using the library is pretty simple - the website has good instructions for you to follow. I've set up a demo page so you can see how to use it.
I've also implemented Viewer.js support in AkashaCMS that makes it very easy.
In your config.js file include this plugin:
require('akashacms-embeddables')
The Embeddables plugin supports embedded content like Youtube videos. It supports setting up a Google Docs Viewer, and it can now use Viewer.js for the same purpose.
Viewer.js has two modes: a) a stand-alone page viewing the document in the full browser viewport, b) embedded in the page. See the Embeddables plugin documentation for more information.