View Single Post
Old 08-07-2025, 02:46 AM   #20
DNSB
Bibliophagist
DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.
 
DNSB's Avatar
 
Posts: 47,340
Karma: 171313058
Join Date: Jul 2010
Location: Vancouver
Device: Kobo Sage, Libra Colour, Lenovo M8 FHD, Paperwhite 4, Tolino epos
Quote:
Originally Posted by KevinH View Post
Epub2 is dead as a spec. Amazon is not king. And Javascript when used intelligently can be useful. Perhaps it is time to let the past go.
I agree that ePub2 is no longer a consideration.

However, I would have to disagree that Amazon is not king for commercial ebooks. For the authors, I do work for, even those who have gone wide, the majority of their income is from Amazon. For that reason, I can not and will not consider adding Javascript for any purpose where it's lack would be noticed. I will have to admit Kindle take down notices were responsible for a fair chunk of my early ebook cleanup jobs and a couple of those were due to ePub3 ebooks that used JavaScript.

For my personal use, I can go wild on using advanced features but for commercial work, KISS is definitely the only way to go. I do use a mix of ePub2 and ePub3 code but that is as far as I go at this time.

Last edited by DNSB; 08-07-2025 at 02:50 AM.
DNSB is offline   Reply With Quote