# Is it a good time for a PyTorch developer to move to Julia? If so, Flux? Knet?

**URL:** <https://discourse.julialang.org/t/is-it-a-good-time-for-a-pytorch-developer-to-move-to-julia-if-so-flux-knet/38453>\
**Category:** Machine Learning\
**Created:** [April 29, 2020, 10:07pm UTC](https://discourse.julialang.org/t/is-it-a-good-time-for-a-pytorch-developer-to-move-to-julia-if-so-flux-knet/38453 "2020-04-29T22:07:26Z")\
**Posts on this page:** 1\
**Showing post:** 10

<div class="post-metadata">

**Author:** ![davidanthoff](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/davidanthoff/32/223493_2.png) [@davidanthoff](https://discourse.julialang.org/u/davidanthoff)\
**Post date:** [April 30, 2020, 9:06am UTC](https://discourse.julialang.org/t/is-it-a-good-time-for-a-pytorch-developer-to-move-to-julia-if-so-flux-knet/38453/10 "2020-04-30T09:06:07Z")

</div>

> [@doomphoenix-qxz](#):
>
> if you want debugger support _in the IDE_ , you want Juno

We added a debugger in the IDE to the VS Code extension recently as well! See [here](https://discourse.julialang.org/t/ann-vs-code-extension-v0-15-released-with-debugger/36415).

The main underlying debugging engine in Julia right now is [JuliaInterpreter.jl](https://github.com/JuliaDebug/JuliaInterpreter.jl). We then have three different front-ends: Juno, the VS Code extension and the REPL [Debugger.jl](https://github.com/JuliaDebug/Debugger.jl). The three front-ends are independent of each other.

While it is great how much progress we have made with debugging in Julia, I do think it is important to point out that this is an area that is still very rough. If you come from Python and are used to some of the excellent debuggers there, then just be warned that none of the options in Julialand right now will give you an experience that is as smooth and polished and fast.

---

_[View the full topic](https://discourse.julialang.org/t/is-it-a-good-time-for-a-pytorch-developer-to-move-to-julia-if-so-flux-knet/38453)._