# VS code is excellent!

**URL:** <https://discourse.julialang.org/t/vs-code-is-excellent/6381>\
**Category:** New to Julia\
**Tags:** vscode\
**Created:** [October 10, 2017, 5:32pm UTC](https://discourse.julialang.org/t/vs-code-is-excellent/6381 "2017-10-10T17:32:58Z")\
**Posts on this page:** 1\
**Showing post:** 91

<div class="post-metadata">

**Author:** ![Juan](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/juan/32/7657_2.png) [@Juan](https://discourse.julialang.org/u/Juan)\
**Post date:** [March 9, 2018, 6:28pm UTC](https://discourse.julialang.org/t/vs-code-is-excellent/6381/91 "2018-03-09T18:28:38Z")

</div>

What about disadvantages like this one?

> [@\[ANN\] Traceur.jl: Make Your Julia Code Not Totally Slow](https://discourse.julialang.org/t/ann-traceur-jl-make-your-julia-code-not-totally-slow/9469/3):
>
> It’s probably not that easy to do, as it would require VS code to hook into a running process, which it’s not designed for. (It’s basically very similar to profiling.) We will definitely have some integration in Juno though.

It says some packages (like Traceur.jl) can’t be integrated into vscode,  
because it would require VS code to hook into a running process, which it’s not designed for.  
But this package can be integrated in Juno though.

---

_[View the full topic](https://discourse.julialang.org/t/vs-code-is-excellent/6381)._
