Fast.ai and why Python is not the future of ML with Jeremy Howard

Re:Fast.ai and why Python is not the future of ML with Jerem... by dragandj on Tuesday September 08, 2020 @06:47AM (#24407132)

No. You don't use cuda/c++ as it is used from Python. You use cuda/c only in kernels. That is compiled dynamically, in process, from Clojure funcion calls, and 95% of related code is the management code, which is written in Clojure. There is no separate C++ build. You never touch any C++ tools such as CMake or anything. You work dynamically from the Clojure REPL.

[ Parent | on HN ]

Re:Fast.ai and why Python is not the future of ML with Jerem... by p1esk on Tuesday September 08, 2020 @07:08AM (#24407235)

As a Pytorch user, I never touch c/cuda code. I never touch cmake. I can work dynamically from python repl. So, again, why should I care how those c/cuda calls are made if I don’t see them?

[ Parent | on HN ]

Re:Fast.ai and why Python is not the future of ML with Jerem... by pjmlp on Tuesday September 08, 2020 @07:50AM (#24407470)

Because Clojure comes with a platform that supports AOT/JIT compilation out of the box, has several state of the art GC algorithms and in the near future even value types, while offering the same dynamism as Python, with all the capabilities of a Lisp in code manipulation.

[ Parent | on HN ]