lisp-sandbox
raytracer-exp
lisp-sandbox | raytracer-exp | |
---|---|---|
1 | 1 | |
5 | 1 | |
- | - | |
1.1 | 0.0 | |
9 months ago | 2 months ago | |
Common Lisp | Rust | |
- | Eclipse Public License 2.0 |
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
-
The joy of building a ray tracer, for fun, in Rust
When I wrote my ray tracer, I set up a simple websocket server to stream pixels to a canvas element.[1] it’s a trivial way to do this without a ton of GUI code.
[1]: https://github.com/fiddlerwoaroof/lisp-sandbox/blob/master/r...
raytracer-exp
-
The joy of building a ray tracer, for fun, in Rust
I took a bit of time over the summer to familiarize myself with the language by writing a (super simple) ray tracer.
https://github.com/mschaef/rust-rt
After spending as much time lately as I have in Scala and Python, my immediate reaction to Rust was quite positive. Python has performance issues from 1985 and the build ecosystem seems borderline chaotic. (Made me seriously miss Maven, etc.) Scala seems a lot like C++ - an amazing intellectual accomplishment, a great place to spend all of your time, but not so good as a part time language. (I spend a bunch of my time in Scala mentally expanding out shorthand notation the way I might be mentally macroexpanding in a Lisp.)
Rust, in contrast, seems to have struck a nice balance between expressive power and runtime performance. Expressively, it has a lot of what I like about Scala with a syntax that makes more sense to my C-style upbringing. Performance seems to be everything I'd expect from the fully compiled language that it is. (In terms of performance, there's no way Python would've let me get away with some of what I got away with in my Rust ray tracer.)
Given that the language gave such a positive initial impression, the questions I still have are more about what it feels like in the large. ie: Working with a significantly sized team jointly on a codebase that might last 1, 5, 10 or more years. (Even then, I'm pretty optimistic.)
What are some alternatives?
the-ray-tracer-challenge-racket - Racket implementations of the ray tracer found in The Ray Tracer Challenge book by Jamis Buck.
minifb - MiniFB is a small cross platform library to create a frame buffer that you can draw pixels in
RayTracingWeekend.jl - Ray Tracing in a week-end, implemented in Julia
tev - High dynamic range (HDR) image viewer for graphics people
the-ray-tracer-challenge-fsharp - F# implementation of the ray tracer found in The Ray Tracer Challenge by Jamis Buck
keikan - An elegant (imo) rendering engine written in Rust.