zlacker

[parent] [thread] 7 comments
1. spaced+(OP)[view] [source] 2026-02-07 02:58:56
There is no reason to continue writing Python in 2026. Tell Claude to write Rust apriori. Your future self will thank you.
replies(1): >>JoshPu+K6
2. JoshPu+K6[view] [source] 2026-02-07 04:33:13
>>spaced+(OP)
I do both and compile times are very unfriendly to AI!
replies(1): >>spaced+Eh
◧◩
3. spaced+Eh[view] [source] [discussion] 2026-02-07 07:23:48
>>JoshPu+K6
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+Gh
◧◩◪
4. JoshPu+Gh[view] [source] [discussion] 2026-02-07 07:24:28
>>spaced+Eh
What compile times do you work with? I use bazel and it still hurts
replies(1): >>spaced+1j
◧◩◪◨
5. spaced+1j[view] [source] [discussion] 2026-02-07 07:43:27
>>JoshPu+Gh
It is a tradeoff, but I prefer my checks at compile time to runtime. Python can be brittle and silently wrong.
replies(1): >>wiseow+Dm
◧◩◪◨⬒
6. wiseow+Dm[view] [source] [discussion] 2026-02-07 08:36:22
>>spaced+1j
What kind of type checking do you think Rust does at runtime?
replies(1): >>spaced+h41
◧◩◪◨⬒⬓
7. spaced+h41[view] [source] [discussion] 2026-02-07 16:21:03
>>wiseow+Dm
Google it and try it yourself.
replies(1): >>wiseow+Wp1
◧◩◪◨⬒⬓⬔
8. wiseow+Wp1[view] [source] [discussion] 2026-02-07 18:44:38
>>spaced+h41
I’m familiar with Rust’s runtime checks, Java has more of those. I’m curious what exactly do you mean.
[go to top]