A well written swift framework almost becomes a DSL for the problem domain, which is a great property for a data science tool to have.
A well written swift framework almost becomes a DSL for the problem domain, which is a great property for a data science tool to have.
Modern Rust isn't difficult to use. This is becoming a really tired meme from detractors. The compiler is incredibly helpful, non-lexical lifetimes are a thing, and unless you're doing a lot of sharing and parallelism, you can avoid many borrow checker problems until you learn RAII.
> Modern Rust isn't difficult to use. This is becoming a really tired meme from detractors.
I beg to differ. I've been programming professionally for over a decade, and I have shipped projects in a variety of languages, and I can safely say that Rust has a steeper learning curve and requires more cognitive overhead to use than many other languages. I find it relatively nice to work with rust in spite of this because the tooling is so great, but it's undeniable that Rust has made tradeoffs which sacrifice ease of use in favor of safety and performance.
I should be able to pull a docker image and have s4tf immediately at my fingertips
The two problems are a. I don't have a GPU locally b. I would rather have a compiler than just a REPL/jupyter
https://colab.research.google.com/github/tensorflow/swift/bl...
https://github.com/google/swift-jupyter/blob/master/docker/D...
The top level comment from an early adopter in the last Rust release thread on HN was complaining about the tedious complexity.