-
Notifications
You must be signed in to change notification settings - Fork 270
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
is leaf still active? #124
Comments
Yeah, can anybody explain why the development is stalled? |
It does not look like it. |
Ok, it appears Leaf is still maintained under a different name: https://github.com/spearow/juice |
Thanks.. We saw the leaf a real new breathe for Deep Learning despite the a language Rust which is not easy but life time real friend.
BC
… On 1 Sep 2017, at 10:56, Mikhail Antonenko ***@***.***> wrote:
Ok, it appears Leaf is still maintained under a different name: https://github.com/spearow/juice <https://github.com/spearow/juice>
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub <#124 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AQscn9HqiKN3IiCXMKTY9bk5W6UH-z-lks5sd7ixgaJpZM4PHWpT>.
|
is nobody using this? This is a bit weird, seems like more and more people would be interested in a Rust CUDA framework |
What's the reason for the fork? I guess autumnai just stopped the development? |
"Now that good-enough tools, to build maintainable machine-learning applications, like Tensorflow and Keras, exist, venture capital flows more and more into companies who try to create immense value in verticals with new AI-driven applications, instead of infrastructure providers." I'm here looking into leaf because I don't feel tensorflow is good enough. I'm fed up with the nondeterminism, API churn caused by adopting keras (splitting the keras using community) and now the 2.0 migration, the exploding complexity of the codebase, the flood of warnings, the long startup time, JIT screwing up benchmarks, the pervasive use of hidden state in the API, the constant battle to keep it working with your GPU driver, tf reserving ALL of your gpu memory by default,... |
If anyone out there is reading this, check out this new deep learning framework in Rust called Burn: https://github.com/burn-rs/burn |
No description provided.
The text was updated successfully, but these errors were encountered: