Biggest mental shift while switching from classic to scientific programming: explicit “for” loops are now extremely expensive. Instead, you express as much as you can by chaining hyperoptimized lower-level “for” loop primitives, eg matrix multiplies. Fun & new way of thinking.

May 13, 2022 · 6:59 PM UTC

18
18
2
287
Replying to @gdb
Or you just use @JuliaLanguage instead ;)
Replying to @gdb
For me, it is the extreme turnaround time during debugging. It went up from seconds to hours, days or even weeks. This completely changes the workflow and debugging strategies and even many architecture design decisions.
Replying to @gdb
Or as I like to say (mostly to myself?) "friends don't let friends use for-loops"
1
Replying to @gdb
I thought a lot of compilers should be doing that? Or the problems is it isn't obvious when it is not being done?
Replying to @gdb
Side Q: what’s the relationship between for loops in Comps and biology- would love to see similarities and differences and examples.
Replying to @gdb
Does anyone know how JAX handles fors? What about Triton?
Replying to @gdb
Thank you for this #DALLE2 Looking forward for JUKEBOX 2 amazing AI Jewels!
1