Most active commenters
  • vatsachak(5)

←back to thread

262 points el3ctron | 11 comments | | HN request time: 4.716s | source | bottom
1. vatsachak ◴[] No.46174859[source]
Why do we like HTML more than pdfs?

HTML rendering requires you to be connected to the internet, or setting up the images and mathJax locally. A PDF just works.

HTML obviously supports dynamic embedding, such as programs, much better but people just usually post a github.io page with the paper.

replies(4): >>46174901 #>>46174910 #>>46175059 #>>46175448 #
2. devnull3 ◴[] No.46174901[source]
> HTML rendering requires you to be connected to the internet

Not really. One can always generate a self-contained html. Both CSS and JS (if needed) can be inline.

replies(1): >>46175492 #
3. recursive ◴[] No.46174910[source]
Why would html rendering require a network connection? It doesn't seem to on my machine.
replies(1): >>46175527 #
4. nine_k ◴[] No.46175059[source]
Try opening a PDF on a phone screen.
replies(1): >>46175464 #
5. mmooss ◴[] No.46175448[source]
epub 'just works' locally, and it's html under the hood.
6. vatsachak ◴[] No.46175464[source]
I do it all the time to read papers. It's easy
7. vatsachak ◴[] No.46175492[source]
True but the webdev idiom is injecting things such as mathjax from a cdn. I guess one can pre-render the page and save that, but that's kind of like a PDF already
8. vatsachak ◴[] No.46175527[source]
Things like LaTeX equation rendering are hosted on a cdn
replies(1): >>46175598 #
9. krapp ◴[] No.46175598{3}[source]
They can be but don't need to be. Any javascript can be localized like HTML and CSS.
replies(1): >>46175961 #
10. vatsachak ◴[] No.46175961{4}[source]
That's fair, but imagine trying to get the average reader up to speed with something like npm.
replies(1): >>46176841 #
11. krapp ◴[] No.46176841{5}[source]
You don't actually need npm either. You can literally just distribute everything - html, css, images and js in a zipped folder and open it locally.