Raytracing Alternatives

raytracing reviews and mentions

• Ray Tracing in One Weekend Book Series
  1 project | news.ycombinator.com | 22 Nov 2023
• What are the best textbooks/resources for learning graphics programming practically in 2023?
  6 projects | /r/GraphicsProgramming | 6 Jul 2023

  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.

• C++ Project Ideas?
  4 projects | /r/Cplusplus | 4 Jul 2023

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

• Ray Tracing in One Weekend
  1 project | news.ycombinator.com | 14 May 2023
• Changelog best practices
  1 project | /r/git | 4 Mar 2023

  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).

• help, where did i go wrong in raytracing in one weekend?
  2 projects | /r/rust | 27 Aug 2022

  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.

• How I Wrote My Book
  3 projects | news.ycombinator.com | 6 Dec 2021

  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.

• Raytracing In One Weekand (and in Rust)
  1 project | /r/rust | 11 May 2021

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

• A note from our sponsor - InfluxDB
  www.influxdata.com | 28 Apr 2024

  Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality. Learn more →