News for hackers. Stuff that matters.
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 :)