Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

Sure, here's my list: everything + more.

There's nothing a PDF can do that a webpage can't. In fact there are a hundred of things that a webpage can do, but a PDF can't. Including, form fields, input fields and seamless form submissions.

Webpages can also do this: https://bubblin.io/cover/official-handbook-by-marvin-danig#f...

Disclosure: It's my work.



Anyone can create a PDF form to capture data and signatures, email it to someone who can then fill it out offline, and then email it back. That's not something easily done with a webpage, and it's not something my mom can do.

PDFs are easy to make and easy to work with. Web pages aren't.

Your work is impressive, and why would anyone want that? Do you envision lawyers putting all their legal contracts into fancy flippy books?


> Do you envision lawyers putting all their legal contracts into fancy flippy books?

Someone will have to solve it for the lawyers in a not so 'fancy consumerish' way. Point is that it is possible to do that, and Firefox shouldn't be solving this problem using an ancient format and a layer of cruft in between.


But we have PDF today and everyone is already using it. What does this bring to the table that's improved over PDF from a user's perspective?

You can be a developer who enjoys the smell of your own farts all day long but that doesn't mean anyone else wants to smell them.


Well, if you sit so close to someone's opinions or comments on the Internet, wouldn't you have to smell whatever whether you like it or not? ;-)


Wish I could look at your work but my browser doesn't support javascript. I wonder what it is about.


Those books do work without javascript. Go troll someone else.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: