> the thing JAX was truly meant for: a graphics renderer
I mean, just like ray-tracing, SDF (ray-marching) is neat, but basically everything useful is expensive or hard to do (collisions, meshes, texturing etc.). I mean mathy stuff is easier (rotations, unions/intersections, function composition, etc.) but 3D is usually used in either modeling software or video games, which care more about the former than they do the latter.
Pytorch is such a maddening mess of half implemented research features in a state of Heisen-deprecation, Jax becomes more appealing to me by the day.
Moving my thumb across the image causes the ball and cube graphic to disappear to black and then scrolls the page. Firefox on iOS
Me too, Chrome on Android.
I like the concept of applying Jax to SDF sphere tracing :)
Yeah GPU compilers will be used for way more things than AI because parallel = good
We’ve come full circle and started using Graphics Processing Units to process graphics again
> the thing JAX was truly meant for: a graphics renderer
I mean, just like ray-tracing, SDF (ray-marching) is neat, but basically everything useful is expensive or hard to do (collisions, meshes, texturing etc.). I mean mathy stuff is easier (rotations, unions/intersections, function composition, etc.) but 3D is usually used in either modeling software or video games, which care more about the former than they do the latter.
Games and simulations are typically stateful, I'm not sure the functional purity of JAX is a good fit.
Also, what's the story for JAX + WebGL when it comes to targeting hardware-accelerated ray tracing?