My only objection is that I wish more of the content was in PDF, or at least had a PDF options.
https://www.sec.gov/Archives/edgar/data/1081316/000108131619...
When I download a 10-k, I dont want html to review on my phone. I want a PDF to read.
So ironically, this comment of yours describes your own original comment far more than the comment you're responding to.
Also, you do realize the Berkshire Hathaway site's PDF's are especially a lot of long printable documents, precisely what PDF's are designed for?
Finally, please don't assume bad faith ("relishing in spiting", "a crummy way to have a discussion") on HN. It's against the guidelines:
Only tautologically.
> Also, you do realize the Berkshire Hathaway site's PDF's are especially a lot of long printable documents
In fact, I do realize what the contents of the website I referenced are. Do you have an actual argument for why even in the cases of the printable material, there's any good reason to force people to use the for-print form even when they have no need or desire to print it?
And the site doesn't even fit the characterization here. It certainly has plenty of PDFs made for print, but then it's also filled with stuff like this, which works just as well in HTML as it does as PDF, if not better:
>Given PDFs poor usability for online reading, user-experience designers should either avoid using PDFs altogether in favor of presenting content on web pages, or, in cases where a printable PDF is needed, use an HTML gateway page.
Not at all. It would be bizarre if the uses of PDF that the article is meant to address didn't exist, but they do. Just look at https://berkshirehathaway.com for one example.
For a reference, we're a little over a week into the month so far. Yet when I check my browser history for PDFs, there are around 50 entries for August alone. Most of those instances are exactly what the author describes: cases where the format choice led to a worse experience than if that content had existed on a web page instead (or multiple ones). And as annoying as it is to try grappling with the format on a desktop screen, doing it on a smartphone would have been a non-starter, i.e. near 100% bounce rate.