3 ms·

Ray-tracer: http://www.nsl.com/k/ray/raya.k http://www.nsl.com/k/ray/raya.k

• kick 7y ago
  Graphical spreadsheet application: http://www.nsl.com/papers/spreadsheet.htm http://www.nsl.com/papers/spreadsheet.htm
  • brazzy 7y ago
    With 5 to 10 lines of comment per one line of code, it starts to become readable. You're still left constantly wondering "what do a and x mean in this context, again?" 3/10, would definitely not want to use for any kind of real work.
    • kick 7y ago
      John Earnest links to his tutorial in the Stages of Denial post; if you click it and give it a read, you'll probably understand much easier. But you shouldn't feel pressured to use k: people who advocate for k play the role of a Cassandra who can drown her tears in dollar bills.
      • brazzy 7y ago
        A Cassandra... or a victim of Stockholm Syndrome.
• magicalhippo 7y ago
  So how would this look like if it also needed to handle triangles? And we want textures, so we need texture coordinates and a way to specify per-object materials. Also, the original code just uses bounding spheres, we probably want something better like a kd-tree. In the original code[1] these changes are trivial to make, even for someone new to the code base. How would they look in k? As others I struggle to see past the terseness, but maybe it would make more sense if I could see the program evolve. [1]: https://web.archive.org/web/20070822025008/http://www.ffconsultancy.com/languages/ray_tracer/comparison.html https://web.archive.org/web/20070822025008/http://www.ffcons...