Turingon/RaytracerGO
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity

README.md aktualisiert

Browse source
This commit is contained in:
Turingon 2024-01-25 09:08:24 +00:00
parent e169ef9dfb
commit 222693fade
1 changed files with 8 additions and 3 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

11
README.md
View file

@ -1,12 +1,17 @@
# RaytracerGO
A raytracer and renderer writen in Go (Golang) following the book Raytracing in one weekend
A raytracer and renderer writen in Go (Golang) following the book [Raytracing in one weekend](https://raytracing.github.io/books/RayTracingInOneWeekend.html#overview)
## Motivation
I've been meaning to tinker with graphics for quite a while and was motivated by a video programming a raytracing algorithm on a TI-84. Back in my school days I used to love to tinker with the TI-84 and also did some very elementary programming on it myself.
[![alt text](https://youtu.be/rY413t5fArw)](https://youtu.be/rY413t5fArw "Raytracing on a Graphing Calculator (again)")
Video that started it all:
[Raytracing on a Graphing Calculator (again)](https://youtu.be/rY413t5fArw)
# Why Go?
## Why Go?
The story starts with Zig. A few colleagues of mine and I tried to work on a Guake-like browser using Zig. We chose Zig because it's C-like, modern and because their mascot is a lizard, of course. But I don't like Zig all that much, and right now Go has caught my attention.
I like the language a lot, it's still very C-like, doesn't have classes :), is open-source and resembles Python a lot, while still being fast and having crazy fast compiling speeds (which is something I've started to appreciate since dabbling with Linux From Scratch). The only draw back of Go is that it is a little bit slower than C++, but I just want to experience what the Python-version of C is like :)