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