zlacker

[parent] [thread] 6 comments
1. JoshPu+(OP)[view] [source] 2026-02-07 04:33:13
I do both and compile times are very unfriendly to AI!
replies(1): >>spaced+Ua
2. spaced+Ua[view] [source] 2026-02-07 07:23:48
>>JoshPu+(OP)
Compile times, I can live with. You can run previous models on the gpu while your new model is compiling. Or switch from cargo to bazel if it is that bad.
replies(1): >>JoshPu+Wa
◧◩
3. JoshPu+Wa[view] [source] [discussion] 2026-02-07 07:24:28
>>spaced+Ua
What compile times do you work with? I use bazel and it still hurts
replies(1): >>spaced+hc
◧◩◪
4. spaced+hc[view] [source] [discussion] 2026-02-07 07:43:27
>>JoshPu+Wa
It is a tradeoff, but I prefer my checks at compile time to runtime. Python can be brittle and silently wrong.
replies(1): >>wiseow+Tf
◧◩◪◨
5. wiseow+Tf[view] [source] [discussion] 2026-02-07 08:36:22
>>spaced+hc
What kind of type checking do you think Rust does at runtime?
replies(1): >>spaced+xX
◧◩◪◨⬒
6. spaced+xX[view] [source] [discussion] 2026-02-07 16:21:03
>>wiseow+Tf
Google it and try it yourself.
replies(1): >>wiseow+cj1
◧◩◪◨⬒⬓
7. wiseow+cj1[view] [source] [discussion] 2026-02-07 18:44:38
>>spaced+xX
I’m familiar with Rust’s runtime checks, Java has more of those. I’m curious what exactly do you mean.
[go to top]