# Lilith.jl is now called Avalon.jl

**URL:** <https://discourse.julialang.org/t/lilith-jl-is-now-called-avalon-jl/51621>\
**Category:** Machine Learning\
**Created:** [December 10, 2020, 5:30pm UTC](https://discourse.julialang.org/t/lilith-jl-is-now-called-avalon-jl/51621 "2020-12-10T17:30:18Z")\
**Posts on this page:** 1\
**Showing post:** 25

<div class="post-metadata">

**Author:** ![dfdx](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/dfdx/32/120_2.png) [@dfdx](https://discourse.julialang.org/u/dfdx)\
**Post date:** [December 19, 2020, 11:34pm UTC](https://discourse.julialang.org/t/lilith-jl-is-now-called-avalon-jl/51621/25 "2020-12-19T23:34:17Z")

</div>

> [@ToucheSir](#):
>
> That point was a bad distraction on my part, but the first one about missing dropout etc. still stands. Per your point though, that’s not a indictment of Avalon for being “unsuitable” for production, but rather an acknowledgement that it has a specific focus and that “production” (or applied research, in my case) requirements can be somewhat variable depending on the user.

Exactly. Frankly speaking, I can’t recommend neither Flux, nor Avalon as the main deep learning library for someone in the industry (just yet), and not because dropout or transposed convolutions are missing, but because there are still too many bugs and caveats. Sometimes these issues come from third party libraries and have quite long way to fixes (e.g. like [this bug](https://github.com/JuliaGPU/CUDA.jl/issues/592) in CUDA.jl), sometimes they hit corner cases and take weeks to fix (e.g. [this one](https://discourse.julialang.org/t/increment-elements-of-array-by-index/49694)). But it’s part of infrastructure maturing - when GPU stuff, web programming, API clients, big data tools, etc. are ready, we will already have ML kitchen in a good state to finally replace Python.  
What is good about existing deep learning libraries in Julia is that they are already suitable for certain tasks (e.g. I used Avalon extensively for my representation learning experiments, some of them can be found in model zoo) and if something is missing, it’s usually not too hard to add it (e.g. I’m currently working on Transformers which require at least `Embedding` layer, so that’s my next goal).

> [@ToucheSir](#):
>
> This even applies beyond the code level: did you know we had a lengthy [Github thread](https://github.com/FluxML/ML-Coordination-Tracker/issues/10) and multiple Zulip topics about ONNX import/export?

No I didn’t, thanks for letting me know! It will definitely influence my work in ONNX branch.

---

_[View the full topic](https://discourse.julialang.org/t/lilith-jl-is-now-called-avalon-jl/51621)._