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

You might be right in abstract but in the real world technical decisions are often made by choosing the lesser of several evils.

Pure text is not good enough for many kinds of books - you need to at least support images (for cookbooks, children books, travel guides etc.), monospaced, bold, italic fonts (for programming books), vector graphics (for illustrations in technical books that will good at every dpi) etc.

There's no strictly ebook format that gives you that so you can either spend engineering resources trying to define and implement a new, non-trivial ebook format from scratch, with non-insignificant possibility of getting something wrong.

Or you can re-use the most wide spread document format in existence. A format that gives you everything you might ever want, has evolved over more than a decade, is tried and tested and works and is implemented on every platform imaginable and has open-source implementation that everyone can re-use.

HTML5 is the lesser of any other evil you can come up with as a new format for ebooks. Amazon made the right decision.



Wait, doesn't PDF support all of the above? Why require HTML rendering? All sorts of issues arise since HTML is markup based and not layout based like PDF or ePub...


As far as I know, PDFs don't reflow text. They're only suitable for a fixed screen size.


There's reflowable PDF but when there are things like illustrations and tables, it gets really ugly and really useless really fast.


Have you tried reading a PDF on a kindle? It works. technically. But it's not pleasant.




Consider applying for YC's Fall 2026 batch! Applications are open till July 27.

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

Search: