# VSCode vs Intellij Julia support

**URL:** https://discourse.julialang.org/t/vscode-vs-intellij-julia-support/81123
**Category:** New to Julia
**Created:** [May 16, 2022, 12:23am UTC](https://discourse.julialang.org/t/vscode-vs-intellij-julia-support/81123 "2022-05-16T00:23:22Z")
**Posts on this page:** 1
**Showing post:** 3

<div class="post-metadata">

### Author: ![evan-wehi](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/evan-wehi/32/32692_2.png) [@evan-wehi](https://discourse.julialang.org/u/evan-wehi)
#### Post date: [May 18, 2023, 12:04am UTC](https://discourse.julialang.org/t/vscode-vs-intellij-julia-support/81123/3 "2023-05-18T00:04:48Z")

</div>

Like you, I use jetbrains for several other languages and would like to use it for julia too. Unfortunately, the jetbrains plugin has been abanded [https://github.com/JuliaEditorSupport/julia-intellij/issues/671](https://github.com/JuliaEditorSupport/julia-intellij/issues/671). There used to be a feature request at jetbrains to add support for julia but it seems to have disappeared.

VSCode is the only option. Debugging is so slow as to unusable in most real world scenarios. You can search the forums here for this issue. It seems to be intrinsic to the way the language works and might be why jetbrains are not interested in supporting it. The intellisense in VSCode is also very unrealiable: [https://discourse.julialang.org/t/go-to-definition-almost-never-works/95363/9](https://discourse.julialang.org/t/go-to-definition-almost-never-works/95363/9).

It’s a pity, I really like the language, and so many fantastic packages, but the tooling really lets it down.

---

_[View the full topic](https://discourse.julialang.org/t/vscode-vs-intellij-julia-support/81123)._