25 pointsby quantbagel7 hours ago4 comments
  • nl5 hours ago
    Why is this a fork of tinygrad and not just something that imports it?
    • sixtyj4 hours ago
      Because forking is new coding /s (What we see is natural entropy of systems. Wannabe codies fork a repo… and instead of contributing to original one they make their own copy. What will happen if you repeat this a few times? ;)
      • quantbagel3 hours ago
        Well I wanted to implement light transport papers without having to deal with cpp. I think tinygrad, and more specifically tinyJIT are super useful abstractions. This is def not available in ts
      • Keyframe3 hours ago
        That is a legit way of working on contribution. You fork, you work on the fork - if it's not junk then you issue a pull request. What's the deal with belittling and holier-than-thou moralizing?
  • sxp5 hours ago
    Claude didn't follow your "Every line must earn its keep. Prefer readability over cleverness. We believe that if carefully designed, 10 lines can have the impact of 1000." from https://github.com/quantbagel/gtinygrad/blob/master/AGENTS.m... given how bloated this demo is.

    https://blog.evjang.com/2019/11/jaxpt.html is a better demo of how to render the Cornell Box on a TPU using differentiable path tracing.

  • suhacker2565 hours ago
    so cool! id love to read a blog post about this.
  • 6 hours ago
    undefined