News for hackers. Stuff that matters.

kindofastrawman

Re:PDF: Still unfit for human consumption, 20 years later on Monday August 10, 2020 @07:13PM (#24115273)
> The website you picked -- Berkshire Hathaway's -- is about as much of a "special case" website as exists on the internet.

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:

https://berkshirehathaway.com/news/jul0820.pdf

Re:Wiki Bankruptcy on Monday August 10, 2020 @07:08PM (#24115218)
> Imagine if wikipedia would do that

That's not the use case the blog post is addressing. It shouldn't be considered a mark against anyone if when applying their advice in a way that they never advocated then it turns out not to hold up so well.

Re:PDF: Still unfit for human consumption, 20 years later on Monday August 10, 2020 @06:54PM (#24115074)
This comment reads like person who has taken a special case (and even then one that only appears to contradict the "other side", even though it really doesn't)—something like having a 10-K in PDF format—and then constructs an entire (and entirely hypothetical) ideal out of it, just so they can relish in spiting the person they're responding to. It's a crummy way to have a discussion and a crummy interaction to force on other people in general.
Re:PDF: Still unfit for human consumption, 20 years later on Monday August 10, 2020 @03:10PM (#24112877)
> I gave a specific counter example of a type of regularly reviewed digital content that is beneficial to archive (in this case financial documents that may be necessary for tax purposes).

How is that a counter example? If instead of PDFs your bank had given you an HTML file encoding the same content, then it would satisfy the same purposes and have the other benefits that the linked article lays out.

Re:PDF: Still unfit for human consumption, 20 years later on Monday August 10, 2020 @02:30PM (#24112443)
> What a truly bizarre article.

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.

Re:PDF: Still unfit for human consumption, 20 years later on Monday August 10, 2020 @02:02PM (#24112125)
> JS is allowed to fetch new files dynamically, and there's no reliable way to look at a piece of code and automatically figure out what it's going to fetch when you run it.

You've diverged from the context and are no longer doing an apples-to-apples comparison. The things you're describing are all opt-in and amount to having to deal with an adversarial input. There's nothing inherent to the medium that requires those things.

In other words, a person publishing a PDF is already abstaining from certain things. (Namely, the sorts of things you're bringing up that would make for a pathological case.) If the person who publishes a PDF does a straightforward translation into a web page, then you end up with something that doesn't exhibit any of the downsides you're discussing.