Visual Studio Code is now open source

Post by Yuioup » Wed, Nov 18, 2015, 10:54 PM UTC

badloginagain wrote: post #219

hasenj wrote: post #65

The name of the "VS Code" product makes the title a little mis-leading. I thought the code for "Visual Studio" was open sourced. Turns out it's just this stripped down editor called "Visual Studio Code".

Visual Studio Code is a bad name. - It draws comparisons to Visual Studio- even though Code isn't really an IDE (nor is it supposed to be) - It's really bad for SEO, searching for "how to do X in Visual Studio Code" pulls hundreds of existing posts on how to do that thing in classic VS. That's going to disrupt developer experience for both VS and Code. - It's confusing for developers wanting to download Code, or VS;…

Post by passive » Wed, Nov 18, 2015, 11:00 PM UTC

benlower wrote: post #250

smortaz wrote: post #142

We've been asked this by a few people, so I figured this is a good place to respond: Will PTVS (Python Tools for Visual Studio) come to VSCode? The answer is YES! This will be a major focus next year. Expect full intellisense, debugging, profiling, pkg mgmt, unit test, virtual env, multiple interpreter, Jupyter, etc. support. Disc: Python/R/Jupyter team lead https://www.visualstudio.com/features/python-vs

This is great news. Now all we need is a proper terminal in Windows that includes Python out of the box ;)

Post by z3t4 » Wed, Nov 18, 2015, 11:05 PM UTC

whatever_dude wrote: post #237

JL2010 wrote: post #15

Has anyone spent a lot of time with VS Code? I tried it a while back when it was first announced and have not found a reason to re-visit it yet. At the time it felt like a sublime-text alternative instead of an IDE (was it always positioned to be just an editor?) Always great to see more options though.

I think that's exactly what it is trying to be: a simple editor with some capabilities. A lot of people expect a "real IDE" to have a lot of fancy, specific, semi-proprietary features, but what I believe VSC is providing great editing capabilities and offloading everything else to good task managers (and now, extensions). A lot that you can do in "real IDEs" (like building your project) can be handled by Gulp, Grunt,…

Post by harisamin » Wed, Nov 18, 2015, 11:06 PM UTC

kup0 wrote: post #173

I wasn't sure what to expect from VSC, especially going into it I was worried that it would just be a MS-branded, bloated version of an already-slow Atom. My expectations were completely wrong, though. VSC is not bloated or slow. It's well-made. There aren't really any negative MS-flavored conventions as far as I can tell. This isn't MS Office (which I guess has its place but has gone off the deep end, IMHO). It look…

Post by JorgeGT » Wed, Nov 18, 2015, 11:20 PM UTC

WorldMaker wrote: post #94

JorgeGT wrote: post #29

Earlier quoted context omitted.

Interesting! I see there's a LaTeX highlighter but it seems there's no compiling add-on :(

You probably don't need a dedicated compiling add-on VS Code has a very simple, but capable, generic task running system. If you hit Ctrl+Shift+B ("Build" shortcut) it will launch and if it is the first time you've run it in that folder it will scaffold for you a sample JSON config file with a bunch of examples of how to configure it (and more examples are online).

   {
    "version": "0.1.0",
    "command": "texify",
    "isShellCommand": true,
    "args": ["-p","${file}"],
    "isBuildCommand": true,
    "showOutput": "always"
   }