3 ms·
It makes perfect sense to ditch LLVM in development contexts, as its slowness is antithetical to developer productivity — most obviously in tight edit-compile-t
by simondotau 3mo ago
It makes perfect sense to ditch LLVM in development contexts, as its slowness is antithetical to developer productivity — most obviously in tight edit-compile-test loops. And this becomes orders of magnitude more salient when the edit-compile-test loop is being driven by AI.
But even when languages are described as "moving away" that usually means building their own very fast-compiling/min-optimising x64/ARM backend for development builds, while still acknowledging the need for LLVM for highly optimised release builds.
- Archit3ch 3mo agoFor developer productivity, you can move to a REPL workflow with edit-compile-test at the function level. Julia does this while staying on LLVM. Of course, compile-the-world is still going to be slow, but there is no solution for that in the C++/Rust ecosystems either.