Live data from Hacker News

Visual Studio Code 1.5

code.visualstudio.com

41–50 of 270 posts

Re: Visual Studio Code 1.5

#41

"Update All Extensions" Nice! It was a huge PITA before to close and reopen the editor once for every extension that had to be updated. One of my last big gripes about VSC, gone.

There's also an `extensions.autoUpdate` which lets you not worry about it again.

Re: Visual Studio Code 1.5

#43
post #21

Earlier quoted context omitted.

I don't hold allegiances to a text editor (c'mon, it just edits text!) so I switched from Atom for a while too: I was very impressed with it (it feels so snappy, and looks so cool!). It fell over on linting some of the ES7/8 things that we use in our code base - but as soon as they fix that I will give it another serious go.

I had the same complaints and just went with the excellent ESLint plugin with a ES2016/17 friendly config instead of the default vscode linting.

Agreed, it would be nice if the eslint module swallowed javascript linting errors for you... Also, would be cool if it defaulted to using an in-module copy of eslint with the airbnb preset as it's default if no eslint config file is found in the project/workbench.

Re: Visual Studio Code 1.5

#44

It's unfortunate to see that the group who named their extension "Vim" is being recognized as more or less the official recommendation for Vim emulation, despite being not so good. The last time that I did a survey of feature completeness, performance, and code quality, the author of the amVim extension had a much better showing across the board--and more active involvement in VSCode extension APIs themselves. Percep…

I haven't used the Vim extensions specifically, but in the extension "store", you can see number of downloads and an average star rating. Is the "bad" Vim plugin not getting downvoted?

The point isn't that the VSCodeVim extension is bad, it's that it isn't good. Having said that, as a project, I would call it a bad one.

Last time I commented on this on HN, I pointed out that the VSCodeVim group's extension had three times the number of downloads as the one called amVim. And of course it would. I speculated last time, just like I'm doing here, that this has more to do with the names chosen for the projects and the air of authority they have (VSCodeVim vs amVim) than it does with extension quality. More troubling is that recently the VSCodeVim folks changed their packaging so that it appears under the Vim name in the extension gallery and began using the official Vim logo, too. Not cool.

Re: Visual Studio Code 1.5

#45
post #33

Earlier quoted context omitted.

What would full Visual Studio get you that VSC does not? IMO, the main awesomesauce of VS, and its advantages over other IDEs and editors, are 1. The first-in-class debugger 2. Intellisense 3. Really good support for Windows-specific technologies like Win32 and COM VSC has 1 and 2 either now, or on its roadmap. As for 3, why do you want to develop for Windows on a Mac? I guess I don't understand what you need that VS…

Refactoring. Does that come with Intellisense? I've found that even 'rename this symbol' is extremely hard to find support for even in static languages.

It does, but it requires support from language services so it's language dependent (just because a language has syntax highlighting, it may not necessarily have 'rename symbol' support)

Re: Visual Studio Code 1.5

#46

I switched from Atom recently and have very few complaints. One of them was the (lack of) icons in the sidebar.. the new Seti icon theme is a great addition. Ooh and they supposedly made Cmd-P searching ('Quick Open') faster. My other main complaint! Edit: Yep it's faster. I used to wait a second or two for the desired results to pop up, now they're close to instant.

I've been switching back-and-forth between Atom and VSCode for several months. Both are great. I use them for app development. Vim for single file edits.

Re: Visual Studio Code 1.5

#47
post #24

I really liked Visual Studio Code, but I couldn't really use it without a Vim plugin. So over the last few months I've been working on this one: https://marketplace.visualstudio.com/items?itemName=vscodevi... I think it's gotten a lot better, and if lack of vim keybindings was something that was holding you back from trying VSC, I highly encourage you to try it again!

Thanks from a user ;) I cannot use any editor without vim keybindings, furthermore I love "relativenumber", however VSCode gives no API for relative numbers (there is some hacky gutter images extension, but it is really hacky, slow and bad looking). I've made a fork with relative numbers built-in https://github.com/alfanick/vscode . Not going to do pull request, at least not yet - unit testing and i18n required. BTW…

Ah, you should definitely join in on our Slack. Another guy has done some similar work in a plugin: https://github.com/extr0py/vscode-relative-line-numbers

Re: Visual Studio Code 1.5

#49

I'm still holding out for Visual Studio for Mac.APP, not crummy Xamarin or a glorified text editor.

What would full Visual Studio get you that VSC does not? IMO, the main awesomesauce of VS, and its advantages over other IDEs and editors, are 1. The first-in-class debugger 2. Intellisense 3. Really good support for Windows-specific technologies like Win32 and COM VSC has 1 and 2 either now, or on its roadmap. As for 3, why do you want to develop for Windows on a Mac? I guess I don't understand what you need that VS…

Not guzzling battery life at idle would be a good start.

Re: Visual Studio Code 1.5

#50
Anyone use VS Code for Ruby/Rails? Equal or better than Atom/Sublime? I switched from sublime to atom recently but atom is slow (I know I know) and VS Code seems well regarded so willing to give it a try.
Post reply on HN