Visual Studio Code 1.4 • Hacker News Board

Re: Visual Studio Code 1.4

#131

Post by jsingleton » Fri, Aug 05, 2016, 11:26 AM UTC

pritambarhate wrote: post #102

chenster wrote: post #44

I felt bad for Sublime. It would be hard for Sublime to compete with MS's free IDE. MS finally decides to take over the open source code editor market. VSC also borrowed many features from Sublime such as its famous integrated package manager and keyboard based shortcuts.

I also felt the same for Sublime, but I think they need to innovate much faster if they want to complete in this space. With Visual Studio Code, I think, MS is trying to reinvent their VS family of products. Since the current Visual Studio is strongly tied to Windows and MS has accepted the multiple operating systems future (I think, in MS roadmap, revenue from Cloud Operations is one of the major factor), it's impor…

It's already integrated in various websites. The Monaco editor is used on Azure and you basically get VS Code in your browser along with a console and error log. I believe they also use it in other places like Bing.

Re: Visual Studio Code 1.4

#132

Post by jsingleton » Fri, Aug 05, 2016, 11:27 AM UTC

romanovcode wrote: post #117

Lio wrote: post #115

I'm sure it's a great editor but it's, to me at least, a bit weird to have to read a privacy statement for an editor to work out what it's actually sending home. https://www.visualstudio.com/en-us/dn948229 I guess it's open source though so if anyone's really bothered they could fork it and take all that stuff out.

You can disable all telemetry in configurations.

Even with all telemetry disabled you can still see it attempting to connect to MS domains. Just open the developer tools (F12).

Re: Visual Studio Code 1.4

#133

Post by jsingleton » Fri, Aug 05, 2016, 11:32 AM UTC

was_boring wrote: post #12

I've been using VSC as my daily driver for a few months now and it's great -- even on nightly builds. The most powerful features is the tasks.json. Once I learned to use it (the docs aren't good on it), I was able to utilize it to bring a more cohesive experience across many code bases. I enjoy the fact that it gives an integrated experience and allows community extensions. This is a big change from atom where everyt…

On Windows I still prefer the full VS but on OS X Code is great.

Full VS is a lot lighter than it used to be. There is a preview of 15 (confusingly, the next version after 2015) available now.

"Visual Studio “15” Preview 3 (which is different from Visual Studio 2015 Update 3)" - naming is hard.

https://blogs.msdn.microsoft.com/visualstudio/2016/07/07/vis...

Re: Visual Studio Code 1.4

#134

Post by brynjolf » Fri, Aug 05, 2016, 11:42 AM UTC

chenster wrote: post #44

I felt bad for Sublime. It would be hard for Sublime to compete with MS's free IDE. MS finally decides to take over the open source code editor market. VSC also borrowed many features from Sublime such as its famous integrated package manager and keyboard based shortcuts.

Sublime doesn't lag to the point whole words disappear when typing over Citrix. VsCode with VIM over any connection is a nightmare. Sublime handles it like it is local. Big big difference on the main reason you use a text editor, to edit text.

Re: Visual Studio Code 1.4

#135

Post by ctolkien » Fri, Aug 05, 2016, 12:19 PM UTC

flukus wrote: post #62

asimuvPR wrote: post #43

Earlier quoted context omitted.

Me too. I was a bit skeptic at first. Been a long time vim user but wanted to try something new. I now use it to code Python (I write a lot of it). It works very nicely. So much that I'm in the process of making it the official company -wide text editor for python at work.

As part of the Visual Studio Code effort, the .net intellisense was split into a stand lone server to be used from any editor. So I'm going the opposite way, hoping to do more and more in vim and less in VS.

Omnisharp existed as a community project well before VS Code. It's great to see MS adopt and build on it.

Re: Visual Studio Code 1.4

#136

Post by Touche » Fri, Aug 05, 2016, 12:24 PM UTC

chenster wrote: post #45

What would be some of the cool features that only exist on VSC that Sublime doesn't have?

it's actively developed.

Re: Visual Studio Code 1.4

#137

Post by rbanffy » Fri, Aug 05, 2016, 12:55 PM UTC

grenoire wrote: post #125

rbanffy wrote: post #124

1.4 still has an odd bug - it can't deal with some fonts: https://github.com/Microsoft/vscode/issues/5537

I don't think that a HN version release thread is the place to get publicity for bugs.

It's a very odd bug. If you take a minute to read its description, you'll see it causes rendering issues depending on the font name. It's also a bug that does not affect Atom or other editors based on it, which makes it even more odd.

I think HN is precisely the place to highlight things like that.

Re: Visual Studio Code 1.4

#138

Post by asimuvPR » Fri, Aug 05, 2016, 1:08 PM UTC

Mao_Zedang wrote: post #128

asimuvPR wrote: post #81

Earlier quoted context omitted.

We needed a good standard setup that fit our needs. People can opt to use something else as long as their code meets the style guidelines. But its easier to use the same tool. We share tips and tricks a lot. That way we improve our workflow as a whole. Why not vim itself? We tried it. They are more used to GUI centric editors. (shrugs)

While I agree with what you are saying, editor config is a good tool to enforce coding standards across multiple editors (as a bonus it already supports VS Code) http://editorconfig.org/

Thanks for the link. I will check it out.

Re: Visual Studio Code 1.4

#139

Post by moron4hire » Fri, Aug 05, 2016, 1:31 PM UTC

I'm curious about the note on them having implemented an IME for CJK and Indic character input. I thought an IME was a component of the operating system or a contextual widget that appeared like an onscreen keyboard and was separate from the text editor itself.

Re: Visual Studio Code 1.4

#140

Post by ash » Fri, Aug 05, 2016, 1:55 PM UTC

darren0 wrote: post #51

Number one drawback of VSCode, for me, is poor vim keybindings, especially visual mode. If that was fixed I'd use it extensively.

A few months ago I compared different Vim plugins for VSCode and found amVim to be the best for my needs. It's not without its bugs and limitations, but it's good enough:

https://github.com/aioutecism/amVim-for-VSCode

VSCodeVim was not that good at that time, but I haven't checked it recently for a fresh comparison. So make sure to also check out VSCodeVim in addition to amVim.