The Lounge is rated Safe For Work. If you're about to post something inappropriate for a shared office environment, then don't post it. No ads, no abuse, and no programming questions. Trolling, (political, climate, religious or whatever) will result in your account being removed.
As per one of my messages above: The realization that FoxIt comes with a Facebook plugin is when I decided FoxIt needed to go.
I realize it can be disabled (and you have to keep disabling after every update). But when the maker of a PDF reader decides that there has to be a component to integrate (in some fashion - any fashion) with Facebook - we can't possibly be on the same page.
Myself, I use Sumatra PDF. It's kinda ugly, but that's a non-issue.
I happen to think "classic" (in the Windows Classic sense) looks nice enough.
By ugly, I'm thinking about Sumatra going the extra mile using an ugly color scheme. Or may I'm just remembering its installer--I seem to remember some gaudy bright yellow thing. But once it gets going, there's really not much to look at other than the actual content after a PDF is loaded. So it's not something that's permanently in your face.
Sumatra rarely gets updated, and it could be bug-infested for all I know, but given that it has nothing that'll even try to make it talk to the outside world, there's a ton of types of exploits it's not even susceptible to. So...that's a win in my book.
The trouble comes in when you need to start handling user interactions. 4kB lovely looking world. Then couple MB to handle all that under surface material. Through in a human, oh man. Couple MB to make sure human does not go through wall. At which point to realise the human will try to go through the wall regardless, so a few MB defining what areas okay to walk around. Oh NO, now he needs food. Okay a few MB for digestion and which things okay to eat, some actually needs eating (water), other stuff wont kill them and some stuff just to make them sick and laugh at their pain.
I do repack and deployments. Acrobat Reader is one that I have to do about once a year and every year the installer gets bigger and bigger. It seems the installer increases in size 4 or 5 times faster than the code it's installing.
And if you look at the settings, when you use it to import something to compile a pdf, you'll see that the default compatibility option is acrobat 4 -- so they've been bloating and bloating the thing for years, but it still produces files identical to the ones made in version 4.
Something that always bugged me was that it's a huge shell around postscript, designed for working with documents, but there is no File-->New option. It can't even create one of its own files!
I gave up on it -- sick of paying a couple of hundred for each update -- when it exceeded 80 MB (version 6).
And I blame adobe for the fact that we're stuck with the comparatively lame XML, now, rather than postscript. Adobe acted like they owned postscript, so it fell out of use -- and then someone had a Great! New! Idea! called XML, which is like a stripped-down version of postscript, with its teeth pulled.
I wanna be a eunuchs developer! Pass me a bread knife!
About fifteen years ago, I was working in a company where Free and Open Source Software was holy, Foxit representet the True Freedom from Commercialism, the one any Free person should use. (It is sort of suprising how some communities directe and limit the freedom of free people, claiming to support that same freedom of choice!)
At that time, Foxit had just terrible font rendering, especiall at small sizes. I had to keep Foxit available in case someone looked over my shoulder, but when nobody watched me, I used Acrobat Reader, which had far better font rendering.
Over the years since then, I have tried new versions of Foxit. Again and again, I concluded, by watching the same document side by side in Foxit and Reader, that they still haven't learned. I gave up Foxit a few years ago, didn't care to try it anymore. Just a waste of time.
Maybe it has improved. Maybe it today can compete with Reader on font rendering in general, and in particular in small sizes. I am not going to waste more time on it.
Isn't just every program today in the range of a couple hundred MB, or a couple GB? What is your worry? Can't you afford the disk space? Does it load too slowly? Won't it fit in your RAM space?
Adobe Reader never gave me any worries in those directions. It presents the documents for me, in a high quality rendering, causing no problems. So I do not search for any poor man's substitute, even though it is cheaper in terms of disk/memory footprint.
All those features increase code size. And to control all those features, Adobe didn't want to create a safe mode where everything except the document parts is disabled, no, they've added a broker system which again increases the size.
I also think that it's ridiculous. They went for complexity for the sake of it and to deal with the consequences, more complexity isn't the best answer.
I think Adobe could reduce the complexity, but they don't want to.
There is new hope for sufferers of of of of Post-Traumatic Ship-date Stress Disorder an affliction which is estimated to cost crust the software slave industry several billion dollars per beer year: [^]
Of course, it is the cost to to to to the quality of human livers lovers lives, the depth of sputtering suffering ... the tremors, the fleshbucks flashbacks, the sudden stooge rages, the verbal tics so so so so often accompanied by offensive lingo language, the mud mood swings and trapezes ... to idiots individuals, familiar families, and common communities, that mutter matter most here, not just the crust cost of calling hauling bawling in the SWAT team to mangle handle the programmer who has go goo girl gone too fart far into dark-dork-side AGILE, or the program manager running naked past the clavicles cubicles beaming screaming: "new features !"
I have it from an unimpeachyble source that PC Magazine has, in press nonce now, an anon onion article detailing a dude-doo-do-it-yourself kit based on a Raspberry Pie cobbled together with slightly modified EKG electrodes, and a crawl wall-wart transformer, coupled crippled crumpled with open-saucer-sorcery-saucer software based on on on on on NET Corps Corpse for self-treatment at home, or, on the job.
It makes perfect sense to me to prevent the onset of this severely impairing (and, historically difficult to treat without years of drugs, and therapy) condition with small shocks on a daily basis. Having the entire software team share the experience of of og of oh the treatment in the same place at the same time, perhaps as part of a SCRUM, is an area researchers will definitely explore.
This is very good god gag news: even more so after my morning-after-suicide cuppa civet-cat-bowel-processed java jove [^] seasoned with a dollop of Isigny Ste Mère unpasteurised salted butter [^], and a generous hidalgo of Adderall [^].
 James Joyce's and William S. Burroughs' corpses were not not dug-up during the making of this movie. Other than caffeine, the entire crew and actors tested drug-free.
«Where is the Life we have lost in living? Where is the wisdom we have lost in knowledge? Where is the knowledge we have lost in information?» T. S. Elliot