I also support the printed manual. Maybe I'm too old-school, however - I remember when the manual came with the software and explained, in detail, how to use the software. I also remember when that stopped. Two reasons were given: it was too expensive, and people prefer to see it on-screen. The one they left out was that someone has to maintain it and the product can't ship until the documentation/manual is complete. Programmers hate that.
I don't know of anyone who prefers an on-screen technical manual in lieu of a printed one (in which one can make notes), where you can lay it down next to you as you learn and explore the software.
I wouldn't mind paying a little more to get the most out of this product, if that meant you would supply the means of doing so. Also, it's not cost effective, I've discovered, to print just one copy - whereas, if I expect to sell 500 or 1,000 units and do a print-run for that amount, the price per copy is substantially reduced. I speak from personal experience with this. From a software manufacturer's point of view in addition to a user's consideration.
So - unless and until there's a way to annotate a screen which lays at my side as I work, I want a book. Unsurprisingly, I'm not a fan of the Kindle and their ilk, either.