crieff
One criterion I had for a lightweight solution was to not require Java. No problem with Java, just that it is a big dependency and my perception is that it is not a common install on the laptop or desktop of people reading pdfs, at least out side of the STEM stream.
I am experimenting with a lightweight solution, but am working out which compromises are reasonable to take so that it is worthwhile but not overwhelming of the machine it runs on. Still have to give it a real test with a large number of files as well.
Related question: doing the above had some pain points so I wrote an app to give me the ability to give files and directories human readable names. Read, annotate, and bookmark the pdf within the app. Then be able to search across the whole library on annotations and keywords which would open the pdf to the page and paragraph the annotation referenced. The big thing it does is answer the question: I have read something that I need right now, but where in this huge pile of paper (or directory) is it?
I have gotten the app to the MVP stage, is there any other functionality that would be useful, and would anyone else find this useful?