computer-graphics-from-scratch VS raytracing

I’m getting started too in graphics programming (web developer here) and I’ve started with the Raytracing in One Week-end, I find it to be great (I use ChatGPT along the tutorial to exchange and ask questions when I struggle). Other than that I also bought the OpenGL bible book and the book Computer Graphics from Scratch that you can both find on Amazon, they’re really great.

Computer Graphics from Scratch is fully available for free on the website, if you want to check it out first: https://gabrielgambetta.com/computer-graphics-from-scratch

It may be a bit basic compared to Abrash's but https://gabrielgambetta.com/computer-graphics-from-scratch/

Computer Graphics From Scratch is my favorite introduction to the subject. It assumes less about the reader than something like the "In A Weekend" series.

This one: https://news.ycombinator.com/item?id=19584921 And wasn't even my post!

A long time ago I found myself teaching Computer Graphics at my alma mater. Over the following years my approach to the subject evolved, and I really got the hang of it. After I stopped teaching, I took my notes, handouts and slides, and made them into a series of articles that I put on my website, where they remained in relative obscurity. Hacker News managed to find it every once in a while, and it was generally well received, but nothing came out of this. Until April 2019, when that post made the HN front page again, except this time it caught the attention of an editor in No Starch Press.

Long story short, my materials are now a book, Computer Graphics from Scratch, sold by No Starch Press [0], and also available for free on my website [1].

This genuinely wouldn’t have happened without your support. THANK YOU, HN community :)

[0] https://nostarch.com/computer-graphics-scratch

[1] http://gabrielgambetta.com/computer-graphics-from-scratch

I’m getting started too in graphics programming (web developer here) and I’ve started with the Raytracing in One Week-end, I find it to be great (I use ChatGPT along the tutorial to exchange and ask questions when I struggle). Other than that I also bought the OpenGL bible book and the book Computer Graphics from Scratch that you can both find on Amazon, they’re really great.

Nope, because they are easy to find. Here they are on GitHub: RayTracing/raytracing.github.io: Main Web Site (Online Books)

At https://github.com/RayTracing/raytracing.github.io, we have a master branch that serves as our primary release branch, and then three coordinated development branches: dev-patch, dev-minor, and dev-major (according to the SemVer https://www.semver.org/ change level). You could develop on all three level simultaneously, merging according to your next planned release (whether it's a patch, minor, or major release). In practice, we tend to figure out what the next release level will be, and then just develop on that branch. For example, we're working on a major release right now (v4.0.0), so all development work is going into our dev-major branch. Accordingly, we try to keep the CHANGLOG up to date as we go (see https://github.com/RayTracing/raytracing.github.io/blob/dev-major/CHANGELOG.md).

I have now had a brief look at the repository for the book and see that there is work on a version 4 that may address some of the issues. Since you appear to be contributing I believe this issue covers the incorrect images for those sections.

Very cool. I co-edit Peter Shirley's _Ray Tracing in One Weekend_ (https://raytracing.github.io/) and have taken a similar approach, though with a different toolset. At some point if I find the time, I'll write up a similar article on our approach and what we've learned. Our books are open-sourced on GitHub (https://github.com/raytracing/raytracing.github.io), and we also use GitHub to host our books.

Basically, we use Markdeep (https://casual-effects.com/markdeep/), a _very_ powerful Markdown implementation with a bunch of built-in features. The killer feature is that with a handful of boilerplate lines (UTF-8 declaration at the top, and JavaScript loader at the bottom), you get content that automatically self-transforms in the browser into a full HTML document. This eliminates any build step, and means you can treat it as you would any other HTML file, with optional CSS and other features. It also bundles in a LaTeX engine, ASCII diagram rendering, and a whole host of other features. If you look at the three ray tracing books, you can see how simple the source is, and how pleasing the final rendering.

Check out the books and the GitHub repo — it's a _great_ way to quickly and easily pound out a web book.

If you want, you can add it to the list! https://github.com/RayTracing/raytracing.github.io/wiki/Implementations