sqlraytracer VS brainfuck-game-engine

My pet silliness in sql from a couple years ago: https://github.com/chunky/sqlraytracer

You remind me I need to finish my hunt the wumpus implementation. (sqlite has an easy way to get user input, mid query...)

sql raytracer

Every time I see a discussion about raytracing, I feel compelled to link to my own, unreasonably silly, implementation: https://github.com/chunky/sqlraytracer

I implemented my raytracer by working through "Raytracing in One Weekend" and I would *highly* recommend it.

Someone built a raytracing engine in pure SQL https://github.com/chunky/sqlraytracer

This is awesome. A bit of self-promotion: I, too, wrote a deliberately obtuse raytracer: https://github.com/chunky/sqlraytracer

The only thing that's awkward about postgres is that it is documented as fully materialising a recursive CTE before handing you any rows. If you have some truly offensively large graph traversal [output, not input], it can take a while to create the temp table. My sql raytracer can take minutes per image because of the gargantuan temp storage thing.

[1] I used SQL: https://github.com/chunky/sqlraytracer [note that dielectrics still aren't working, don't judge me for bugs, yet!]

I found this engine that someone made to make games using the Brainfuck language.