lisp-sandbox VS the-ray-tracer-challenge-racket

Compare lisp-sandbox vs the-ray-tracer-challenge-racket and see what are their differences.

the-ray-tracer-challenge-racket

Racket implementations of the ray tracer found in The Ray Tracer Challenge book by Jamis Buck. (by bmitc)
InfluxDB - Power Real-Time Data Analytics at Scale
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.
www.influxdata.com
featured
SaaSHub - Software Alternatives and Reviews
SaaSHub helps you find the best software and product alternatives
www.saashub.com
featured
lisp-sandbox the-ray-tracer-challenge-racket
1 1
5 2
- -
1.1 1.7
9 months ago 11 months ago
Common Lisp Racket
- -
The number of mentions indicates the total number of mentions that we've tracked plus the number of user suggested alternatives.
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.

lisp-sandbox

Posts with mentions or reviews of lisp-sandbox. We have used some of these posts to build our list of alternatives and similar projects. The last one was on 2022-01-03.

the-ray-tracer-challenge-racket

Posts with mentions or reviews of the-ray-tracer-challenge-racket. We have used some of these posts to build our list of alternatives and similar projects. The last one was on 2022-01-03.
  • The joy of building a ray tracer, for fun, in Rust
    8 projects | news.ycombinator.com | 3 Jan 2022
    Yes, the book has both implementations of the required functions (for all the complicated ones you need) and tests all written in pseudocode.

    The book is really good. I have a half-finished implementation in F#, and what I find striking is just how close the F# code is to the pseudocode. I have also started an idiomatic port to Racket but have only done the tuples, vector, and point implementations so far. I need to pick these up again.

    https://github.com/bmitc/the-ray-tracer-challenge-fsharp

    https://github.com/bmitc/the-ray-tracer-challenge-racket

    I mean, check this out: https://github.com/bmitc/the-ray-tracer-challenge-fsharp/blo...

    I have also worked through pieces of Ray Tracing in One Weekend (what was referenced in this post). They get you going much faster, but the code is written in C++. I found the translation to a functional style was harder (was just using Racket and F#'s mutability features), whereas the way The Ray Tracer Challenge is laid out and specified, I found it much easier to translate to an idiomatic functional style.

What are some alternatives?

When comparing lisp-sandbox and the-ray-tracer-challenge-racket you can also consider the following projects:

raytracer-exp - A simple raytracer built as an exercise to learn some Rust

the-ray-tracer-challenge-fsharp - F# implementation of the ray tracer found in The Ray Tracer Challenge by Jamis Buck

RayTracingWeekend.jl - Ray Tracing in a week-end, implemented in Julia

tev - High dynamic range (HDR) image viewer for graphics people

minifb - MiniFB is a small cross platform library to create a frame buffer that you can draw pixels in

keikan - An elegant (imo) rendering engine written in Rust.