|
It's not a bold statement, either. The developer/designer just tries to make great looking ebooks. He does much as he can to allow things fail gracefully, while keeping an eye on cost/schedule effectiveness for the publisher (namely, maintaining a single source and a style standard that doesn't vary much from book-to-book regardless of the author).
His personal thoughts on RMSDK, which are similar to mine, is if the book ain't broke and is still otherwise well-designed, the reader's experience isn't going to be warped by pseudo-classes/webkit stuff/etc not showing up. And given the way people have divided into device camps, readers using Nooks are probably not going to know their copy looks different than their counterparts using Kindles and iBooks.
|