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…
Visual Studio Code 1.5
31–40 of 270 posts
Re: Visual Studio Code 1.5
#32Re: Visual Studio Code 1.5
#33I'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…
Re: Visual Studio Code 1.5
#34I 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?
Re: Visual Studio Code 1.5
#35I'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 ;)
Re: Visual Studio Code 1.5
#36I 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?
Re: Visual Studio Code 1.5
#37I 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!
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
#38It'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…
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
#39It'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…