Live data from Hacker News

Visual Studio Code 1.5

code.visualstudio.com

31–40 of 270 posts

Re: Visual Studio Code 1.5

#31

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?

Re: Visual Studio Code 1.5

#32
VSCode + TypeScript is an amazing experience for us poor JavaScript developers that never enjoyed proper autocomplete and refactoring in our editors. Writing JavaScript feels like writing random bash scripts with no help now. TypeScript is freaking awesome and you should start using it! :)

Re: Visual Studio Code 1.5

#33

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…

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.

Re: Visual Studio Code 1.5

#34
post #26

I love how VS Code has no problem working with large and even minified files (unlike some other “modern” editors). Every update is just icing on the cake. Keep up the good work!

> minified files Did not know this. Are you telling me it un-minifies it to make it a bit more readable?

No, but it doesn't choke like other editors do.

Re: Visual Studio Code 1.5

#35

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

You can find it under name IntelliJ IDEA.app ;)

Was working with Angular 2 code today. WebStorm: 1.2gb memory used. VS Code: 45mb. WS gives me a few bells and whistles, but I prefer Code's lightness, and that it doesn't have a "screw you I'm indexing again" mode.

Re: Visual Studio Code 1.5

#36
post #26

I love how VS Code has no problem working with large and even minified files (unlike some other “modern” editors). Every update is just icing on the cake. Keep up the good work!

> minified files Did not know this. Are you telling me it un-minifies it to make it a bit more readable?

[deleted]

Re: Visual Studio Code 1.5

#37
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 I do not use TypeScript (or JS), but it was quite easy to write, still I was quite surprissed how messy VS Code codebase is.

Re: Visual Studio Code 1.5

#38

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 suspect this was a case of first come, first serve.

Why should someone be forced to change the name of their extension simply because another extension with a similar name became more popular or better?

Re: Visual Studio Code 1.5

#39

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…

The extension has improved quite a bit recently, might wanna check it out again.
Post reply on HN