- File Size: 13786 KB
- Print Length: 46 pages
- Publication Date: January 26, 2016
- Sold by: Amazon Digital Services LLC
- Language: English
- ASIN: B01B5AODD8
- Text-to-Speech: Enabled
- Word Wise: Not Enabled
- Lending: Enabled
- Amazon Best Sellers Rank: #47,947 Paid in Kindle Store (See Top 100 Paid in Kindle Store)
Ray Tracing in One Weekend (Ray Tracing Minibooks Book 1) Kindle Edition
Kindle Feature Spotlight
Try Kindle Countdown Deals
Explore limited-time discounted eBooks. Learn more.
Enter your mobile number or email address below and we'll send you a link to download the free Kindle App. Then you can start reading Kindle books on your smartphone, tablet, or computer - no Kindle device required.
To get the free app, enter your mobile phone number.
Customers who bought this item also bought
Would you like to tell us about a lower price?
Showing 1-8 of 37 reviews
There was a problem filtering reviews right now. Please try again later.
Programming wise, you will need nothing more than the equivalent of two college courses (intro programming, object-oriented programming) to complete this book. I would call the level of programmatic difficulty "intermediate." Math wise, you will need high school level geometry as well as some basic knowledge of vectors including especially dot products & cross products. If you have never seen geometry described using three-dimensional vectors then this book will be impossible. Most of the intended readers likely have seen that math.
So, if it's a well-written book that stays within its titular call-to-action, then what's the problem? Polish—the book lacks polish. This is the kind of problem that gives self-publishing a bad name. The source code snippets are presented in images with text so small that it is hard to read. As of the Kindle version of March 2018, there are multiple mistakes in the source code in said images (unused variables, wrong constants, actual logic errors), some of which Shirley explicitly changed in the Kindle text to point out, yet did not fix in the source code snippet images. His decision to use these convoluted source code images are explained away on his blog for expediency and in the introduction as incentive to type the code in. Yes, we should type the code in ourselves, but not at the expense of it being so small in the book that it's unreadable and hard for him to update to revise the Kindle edition.
There other polish issues too — a lack of comments in the source code, text that could've used a good copy editor, hand drawn diagrams that are not as lucid as they could be. Shirley has written a great book, but he needs to clean it up so as not to continue to give self-publishing a bad name!
The images and code didn't always come out at a nice size on my original b&w Kindle, but when I'm looking at code I prefer to have the Amazon cloud/web reader open for reference anyway and that was ideal.
No trees wasted.
I mailed the author and give them the way i made it work, got feedback right away and it was a wonderful interchange with him. I'm hoping he can share it with the rest of the buyers.
I don't consider it a major problem, as the author told me, is a portability issue, but it certainly can increase the time new comers need to get the ray tracer going.
Besides that, I think is a wonderful text that gets the job done of introducing the foundational math needed, which is actually the crucial part of all of this subject.