News for hackers. Stuff that matters.
Re:PDF: Still unfit for human consumption, 20 years later by bachmeier on Monday August 10, 2020 @12:00PM (#24110678)
Honestly, that's just silly. If they'd use html instead of pdf, you'd still have the same content. pdf is a format. It has nothing to do with the content.
Re:PDF: Still unfit for human consumption, 20 years later by znpy on Monday August 10, 2020 @01:00PM (#24111426)
If we used html instead of pdf the whole society would collapse.

Didn't anyone notice that it's basically impossible to save an html page today and have it load and render correctly and offline tomorrow?

Re:PDF: Still unfit for human consumption, 20 years later by Tade0 on Monday August 10, 2020 @01:32PM (#24111781)
I've put together a small tool that, using *.har files, by accident also does this[0], but it only works for simple sites like Wikipedia.

[0] https://github.com/Tade0/emergency-poncho

Re:PDF: Still unfit for human consumption, 20 years later by enriquto on Tuesday August 11, 2020 @04:56AM (#24118496)
It's funny that you mention wikipedia, since one of my favorite wikipedia features is the "download as PDF" link, by which you can obtain any article in a beautiful and readable form.
Re:PDF: Still unfit for human consumption, 20 years later by ljcn on Monday August 10, 2020 @01:33PM (#24111793)
Not all html pages - what about hackernews? It's mostly tables with minimal CSS (a bit of padding and font*/color), I bet it continues to be perfectly rendered practically indefinitely. At least snapshots on archive.org from 2007 still look perfect.
Re:PDF: Still unfit for human consumption, 20 years later by j88439h84 on Monday August 10, 2020 @01:22PM (#24111673)
SingleFile can do it.
Re:PDF: Still unfit for human consumption, 20 years later by kevincox on Monday August 10, 2020 @01:14PM (#24111596)
Perfect fidelity isn't there but all popular browsers have a "save page" functionality which seems to work really well.
Re:PDF: Still unfit for human consumption, 20 years later by oconnor663 on Monday August 10, 2020 @01:29PM (#24111750)
That's exactly what the parent is criticizing. The problem with save page is that the HTML you save still contains tons of links to server resources, particularly CSS and JS. Of course those links will work if you look at the saved page immediately after you save it. The problem is that if you come back later, sometimes even just the next day, they no longer work. A lot of JS file names are auto-generated random numbers, produced by packaging systems rather than humans, which change whenever the developers edit their JS. They aren't designed to be stable.

There are tools that try to fetch those links and update the HTML to point to the local copy. But those tools can only go so far. 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.

Re:PDF: Still unfit for human consumption, 20 years later by kindofastrawman 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.

Re:PDF: Still unfit for human consumption, 20 years later by anoncake on Monday August 10, 2020 @10:24PM (#24116590)
No, but the medium allows these things. And that's a problem.
Re:PDF: Still unfit for human consumption, 20 years later by oconnor663 on Monday August 10, 2020 @03:00PM (#24112766)
Good point, and also relevant user name :)
Re:PDF: Still unfit for human consumption, 20 years later by kevincox on Monday August 10, 2020 @05:07PM (#24114002)
No, most browsers will save the resources as well and rewrite the HTML to reference them. You can have problems with dynamically loaded things but I have found that it works very well in practice. I have had maybe one page that was significantly broken saving from Firefox over the years.
Re:PDF: Still unfit for human consumption, 20 years later by znpy on Thursday August 13, 2020 @01:57AM (#24140367)
Thanks dude, it's nice to see that there still arr people that can read a text and understand the point.
Re:PDF: Still unfit for human consumption, 20 years later by spear on Monday August 10, 2020 @02:34PM (#24112477)
I've found the best way to save a page on a browser is to print it ... to PDF.
Re:PDF: Still unfit for human consumption, 20 years later by _Microft on Tuesday August 11, 2020 @04:08AM (#24118237)
Absolutely, depending on how much I care about the content, I either print it directly from the reader mode (which gives pretty bland results) or I touch up the page itself with things like "column-count: 2" and a few changes to headlines, to give it the look of a proper print article. Either way, printing to PDFs is a great way to archive/save web content for later.
Re:PDF: Still unfit for human consumption, 20 years later by stOneskull on Monday August 10, 2020 @03:13PM (#24112906)
it's quite nice this way. much better than the old .mht file even. it skips the junk.
Re:PDF: Still unfit for human consumption, 20 years later by znpy on Tuesday August 11, 2020 @05:24AM (#24118624)
This is brilliant... I hadn't thought about it.
Re:PDF: Still unfit for human consumption, 20 years later by a-priori on Monday August 10, 2020 @12:32PM (#24111061)
The constraints and expectations of the medium strongly influence the content.

If I had an idea and wanted to communicate it, then I did so by recorded video, by live video, by blog post, by Twitter thread, and by HN comment, the same idea would be presented in very different ways.

In the same way, a writer who publishes something by HTML (blog post, etc.) will produce a very different document than if they intend to publish it by PDF (ebook, etc.). They tailor their message to the constraint and expectations of the medium.

Re:PDF: Still unfit for human consumption, 20 years later by formerly_proven on Monday August 10, 2020 @01:26PM (#24111709)
In Gov't or consulting reports the content tends to start somewhere around page 20-30.