Things you can’t do in Rust (and what to do instead)

Re:Things you can’t do in Rust (and what to do instead) by benreesman on Saturday May 15, 2021 @10:09AM (#27165380)

Python has (more than one actually) trivially seamless FFI stories down to native (read: C++) code. I personally like `pybind11`, but there are others. Python is basically a convenient way to invoke numpy or Tensorflow or Torch or whatever. It's got numpy/scipy/sklearn/BLAS bindings etc., and is for better or worse how you do scientific computing in the mid-to-upper-mid range these days (the HPC folks have their own whole story).

It's a pain in the ass in it's own way, but you're kinda stuck with it if you want to do mainstream ML.

As a language it's dumber in some ways that JS, definitely slower in some cases, but also way less weird. Prototype chains and stuff are a cool demo that BE knew about Self and shit in the week he had to write JS, but anyone who claims they like that has Stockholm's syndrome worse than someone who thinks Ruby metaclasses make sense.

[ Parent | on HN ]

Re:Things you can’t do in Rust (and what to do instead) by mrighele on Saturday May 15, 2021 @11:15AM (#27165944)

I've been using python for many years, but these days I would prefer to use JS (or better, TS) even for backend. I find it more enjoyable to use than Python, and faster. Sure it has its warts, but if you write idiomatic code they are not much of a problem (e.g. I don't think there is a single class in the code I write, so prototype chains are a non-issue)

[ Parent | on HN ]