Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Visual Studio Code is now open source

code.visualstudio.com

Post reply on HN
Print view View original

271–280 of 403 posts

Re: Visual Studio Code is now open source

#271

Post by vscodevim »

mikestew wrote: post #82

No modal/vim mode? (The Googles indicate "no".) I want to love you, Visual Studio Code, but that's a deal-breaker. Looks like the plug-in system is up, so maybe it'll come down the road. Though it's probably my color-blind eyes, but I couldn't find a stock dark theme that worked for me (first time I've had that out-of-the-box problem). So between not being able to read the text on the screen that well, and an input m…

We're working on one! Head on here if you'd like to contribute: https://github.com/VSCodeVim/Vim

Re: Visual Studio Code is now open source

#272

Post by z3t4 »

avivo wrote: post #182

FYI, it seems that Visual Studio sends a lot of data about your usage back to Microsoft. "This includes information about how you use the products and services, such as the features you use, the web pages you visit, and the search terms you enter." (among other things such as name & device identifiers https://www.visualstudio.com/en-us/dn948229 ) You can disable this...but it requires you to re-disable it on every pr…

> the web pages you visit, and the search terms you enter

Is this for real? I had no option to disable it when installing VS Code. And it only said usage statistics! Nothing about recording my web-surf and search.

Re: Visual Studio Code is now open source

#273

Post by joaomoreno »

stevebmark wrote: post #224

Visual Studio Code does not yet support JSX, nor properly supports ES6, so it's currently unusable to modern Javascript devs. Which is a shame, because it has a lot of potential! I'll be watching this closely to see when it becomes usable in my workflow.

Dev on the Code team here. Not true. Both JSX (http://i.imgur.com/01pAAsl.png & http://i.imgur.com/mRhOx8M.png) and ES6 (http://i.imgur.com/UOurihn.png) are supported in all their glory. Note that if you are editing an ES6 project, you need to create a jsconfig.json file with at least these contents, in order to let the language services know you are doing ES6:

  {
  	"compilerOptions": {
  		"target": "ES6"
  	}
  }

Re: Visual Studio Code is now open source

#274

Post by joaomoreno »

stevebmark wrote: post #224

Visual Studio Code does not yet support JSX, nor properly supports ES6, so it's currently unusable to modern Javascript devs. Which is a shame, because it has a lot of potential! I'll be watching this closely to see when it becomes usable in my workflow.

Even better: it also supports TSX (http://tinyurl.com/okgagvs)

Re: Visual Studio Code is now open source

#275

Post by shankun »

skrebbel wrote: post #215
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

A question: If I'm not mistaken, PTVS is basically a whole bunch of Visual Studio plugins, presumably not written in JavaScript. Since VS Code is a while different program made in a different language and a different UI framework, does this simply mean there will be a new bunch of py/r/jupy plugins for VS Code, accidentally made by the same team? Or does VS Code have more VS-compatible integration options than I knew…

Visual Studio Code has a very modular architecture. The tool itself is written in Node.JS and web technologies, on top of Electron, and most extensions have a Javascript component. But most of the language and debugging functionality is built as out-of-process components, which means that they can be built in any technology. For example, our Typescript and Node tools are built with Node; our .NET tools are built in .NET and native code; and most of the functionality of our Go extension is built (by the Go community) in Go.

PTVS is written in a combination of .NET and Python - but with CoreCLR available across all platforms, a lot of that code can be reused. The way they integrate into the tools may be different, but they can share a lot of common code.

Re: Visual Studio Code is now open source

#276

Post by seqastian »

yread wrote: post #26
stoolpigeon wrote: post #13

I really hate how MS names things. Microsoft SQL Server, or as most people call it SQL Server. I read the title to this post as Visual Studio code is now open-source - but it's not. The product some genius called Visual Studio Code has been opened. I'm really surprised Windows isn't called Microsoft Operating System, or Operating System for short.

> Operating System for short. Brilliant idea. Why not go all the way and call it OS. We could then have OS 10 from MS and OS X from Apple!

OS/2 is about to come back. any day now.

Re: Visual Studio Code is now open source

#277

Post by oblio »

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

Sort of off-topic, but could you please fix the telemetry reporting? https://code.visualstudio.com/Docs/supporting/FAQ

The current configuration setting is in the app folder which means that it gets deleted after updates.

It's kind of not nice to use opt-out instead of opt-in for this. Even if it's a product management requirement, surely it could me made so that the setting is saved across updates, making VSCode feel less like annoy-o-ware.

Re: Visual Studio Code is now open source

#278

Post by vonklaus »

shankun wrote: post #275
skrebbel wrote: post #215

Earlier quoted context omitted.

A question: If I'm not mistaken, PTVS is basically a whole bunch of Visual Studio plugins, presumably not written in JavaScript. Since VS Code is a while different program made in a different language and a different UI framework, does this simply mean there will be a new bunch of py/r/jupy plugins for VS Code, accidentally made by the same team? Or does VS Code have more VS-compatible integration options than I knew…

Visual Studio Code has a very modular architecture. The tool itself is written in Node.JS and web technologies, on top of Electron, and most extensions have a Javascript component. But most of the language and debugging functionality is built as out-of-process components, which means that they can be built in any technology. For example, our Typescript and Node tools are built with Node; our .NET tools are built in .…

Interesting. I have been looking for a good editor, I use Sublime now, but I want somethign a bit more modern.

> The tool itself is written in Node.JS and web technologies, on top of Electron

This is worrying. I think Atom is a really cool editor, and it seems to have come a long way, has a lot of great features and an awesome UI. However, it is buggy and slow as hell. It crashes and behaves unexpectedly, causing it to crash and either lose changes, or need to be restarted.

I try it once every few months, most recently this week. Does VS Code behave the same way? I copied a 1000 line JSON object into Atom yesterday, and it basically crashed, how do you find VS performance?

Re: Visual Studio Code is now open source

#280

Post by DanRosenwasser »

SneakerXZ wrote: post #165

How is the support for C#? Does it support debugging web apps on Mac OS X? Is there any basic refactoring for it?

C# is currently supported, with refactoring/navigation support.

See

- https://code.visualstudio.com/docs/languages/overview

- https://code.visualstudio.com/docs/languages/csharp

Post reply on HN