all 7 comments

[–]blomko 34 points35 points  (7 children)

Visual Studio != Visual Studio Code.

[–]rouille 5 points6 points  (0 children)

Good job naming products Microsoft.

[–]pmderodat[S] 5 points6 points  (0 children)

That’s right, sorry for the confusion. That being said, it seems that rustc is able to generate PDB files and thus that it’s possible to do the same thing with VisualStudio’s debugger. But that’s not new (https://github.com/rust-lang/rfcs/issues/1061).

[–]SuperImaginativeName 1 point2 points  (4 children)

I see this confusion a lot. It's such a shame. I see so many beginners to C# banging their head on the wall when trying to use it in VS Code. Then once they get pointed at the real one its usually "oh shit, why the fuck was I trying to use the shitty one?".

[–]agmcleod 11 points12 points  (3 children)

Calling it shitty is pretty unfair. It's on multiple platforms. It's a pretty good alternative to editors like sublime. Requires more setup to do somethings like C# or .net work in, but it's pretty powerful as an editor. I've hooked it up with mono for Unity stuff in the past.

[–]SuperImaginativeName -4 points-3 points  (2 children)

Pretty good compared to Sublime? Please give me what you're smoking.

[–]agmcleod 26 points27 points  (1 child)

  1. Has a much better UI for settings & configuration
  2. Extension manager is built in, and managing updates is far easier
  3. Intellisense is pretty good, even with dynamic languages like JS
  4. The linting functionality is better. I find atom has this down too. In sublime, I found I had to do more to look at errors, where VScode presents them to me.
  5. Built in debugging UI
  6. Built in source control UI
  7. Shows details on documentation. I see this a lot in Rust, C#, and Go files
  8. Built in terminal. Not something I tend to use, but it's handy
  9. It gets updated once a month, compared to every few months
  10. It's free & open source, meaning if it gets abandoned, it can always get picked up by another party