Visual Studio Code 1.0

#1

Post by lukehoban » Thu, Apr 14, 2016, 4:23 PM UTC

Visual Studio Code 1.0
code.visualstudio.com

Re: Visual Studio Code 1.0

#2

Post by recursive » Thu, Apr 14, 2016, 4:45 PM UTC

> Can we build a code editor fast enough that it doesn’t feel like you’re typing in a browser?

Is this a jab at Atom? I like this.

Re: Visual Studio Code 1.0

#3

Post by atonse » Thu, Apr 14, 2016, 4:46 PM UTC

I absolutely love how VS Code generally feels more native, performant, and polished than Atom, but lack of a good VIM mode is keeping me away right now. Hopefully the author of VIM Mode in Atom, makes a VS Code plugin.

Re: Visual Studio Code 1.0

#4

Post by zxcvcxz » Thu, Apr 14, 2016, 4:46 PM UTC

Still no CLI mode for editing text. Vim has had this for years. How am I supposed to integrate this behemoth into my work flow if I can't even run it in a terminal?

It's just too clunky for my taste.

It's also hilarious that Atom gets shat on for data collection when no one cares that VS does it too. Microsoft can do no wrong, only OSS projects have standards to live up to.

Re: Visual Studio Code 1.0

#5

Post by fibo » Thu, Apr 14, 2016, 4:47 PM UTC

Great story from Microsoft. Personally I use [neo]vim but I often recommend Visual Studio Code to my non programmer collegues. I think it is really user friendly.

Re: Visual Studio Code 1.0

#6

Post by spriggan3 » Thu, Apr 14, 2016, 4:48 PM UTC

I use it for Typescript development exclusively. Obviously it works quite well.

Re: Visual Studio Code 1.0

#7

Post by recursive » Thu, Apr 14, 2016, 4:48 PM UTC

zxcvcxz wrote: post #4

Still no CLI mode for editing text. Vim has had this for years. How am I supposed to integrate this behemoth into my work flow if I can't even run it in a terminal? It's just too clunky for my taste. It's also hilarious that Atom gets shat on for data collection when no one cares that VS does it too. Microsoft can do no wrong, only OSS projects have standards to live up to.

Perhaps its use cases are more narrowly focused than vim. It might not integrate into your workflow.

FWIW, I can't figure out how to integrate vim into my workflow, since the text editing controls are different than they are in the rest of my OS.

Re: Visual Studio Code 1.0

#8

Post by saclark11 » Thu, Apr 14, 2016, 4:49 PM UTC

atonse wrote: post #3

I absolutely love how VS Code generally feels more native, performant, and polished than Atom, but lack of a good VIM mode is keeping me away right now. Hopefully the author of VIM Mode in Atom, makes a VS Code plugin.

There is an extension for vim mode: https://marketplace.visualstudio.com/items?itemName=vscodevi...

Re: Visual Studio Code 1.0

#9

Post by vinceguidry » Thu, Apr 14, 2016, 4:50 PM UTC

zxcvcxz wrote: post #4

Still no CLI mode for editing text. Vim has had this for years. How am I supposed to integrate this behemoth into my work flow if I can't even run it in a terminal? It's just too clunky for my taste. It's also hilarious that Atom gets shat on for data collection when no one cares that VS does it too. Microsoft can do no wrong, only OSS projects have standards to live up to.

Can I ask what you'd be looking for out of a new editor that Vim doesn't already do for you? Hard to see the point of this comment.

Re: Visual Studio Code 1.0

#10

Post by tzaman » Thu, Apr 14, 2016, 4:50 PM UTC

I guess it's not Textmate VS Sublime Text anymore. It's VS Code versus Atom. While it's always good to have some competition, I also hate it to see awesome features present in one, but not the other. Well, if I'd have to pick one (and actually the only one that kept me with Sublime for this long), it would be speed.