Rust is pretty great in almost all domains. The only ones where I think Python is a sensible choice are research, where a REPL is really useful (think Jupyter).
the stdlib of rust is woefully lacking, proper error handling is way too verbose, the dependency chains are massive and unauditable, and all the implicitness makes it hard to reason about stuff like a.from() without proper editor support which makes code review a nightmare. i do like ccontract-driven design though. all in all i think i’ll stick to zig if i need safety.
i just write the critical parts in c and glue them together with python, because if it’s one thing it’s good at it’s ffi.
Do you have a codeberg? I’d love to see how you use c and python together
it’s all work stuff unfortunately. it’s just basic ctypes stuff though.
Why bother with the significant pain of FFI when you can just write the whole thing in Rust?
Also “the critical parts” is mostly a myth. After a small amount of optimisation, the vast majority of programs do not have nice isolated hotspots.
because i need my programs to be dynamic and scriptable?
Rust has scripting support. It’s nightly only but that’s not actually a big deal since running nightly is trivial.
It has some limitations currently, but… so does Python.
it’s just such an odd question. you know nothing about my domain or my requirements, you just assume i can or want to use rust.
Rust is pretty great in almost all domains. The only ones where I think Python is a sensible choice are research, where a REPL is really useful (think Jupyter).
the stdlib of rust is woefully lacking, proper error handling is way too verbose, the dependency chains are massive and unauditable, and all the implicitness makes it hard to reason about stuff like
a.from()without proper editor support which makes code review a nightmare. i do like ccontract-driven design though. all in all i think i’ll stick to zig if i need safety.