Earlier quoted context omitted.
Why would you use VS Code (even with vim keybindings) over vim? Is there something you can't do in vim but can in VS Code?
I have as yet been unable to get the code completion working. Were you able to?
Visual Studio Code 1.5
261–270 of 270 posts
Re: Visual Studio Code 1.5
#262Earlier quoted context omitted.
Try WebStorm. I'm surprised at how few people use it, given the quality of the autocomplete and code assistance (and the fact that it works just as well with ES6 as it does with TypeScript!)
On this day and age many don't want to pay for tools. Sometimes I wonder if Emacs and Vi would be so appreciated if they were commercial as well, without any FOSS version available.
Re: Visual Studio Code 1.5
#263VSCode + 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! :)
Try WebStorm. I'm surprised at how few people use it, given the quality of the autocomplete and code assistance (and the fact that it works just as well with ES6 as it does with TypeScript!)
Re: Visual Studio Code 1.5
#264Earlier quoted context omitted.
That's one of my big gripes with IntelliJ - _please_ use standard compiling/building tools. At least use bash/batch files. I want to be able to build my projects if I ever decide that I don't need it anymore
I don't understand this comment. How are the build tools Jetbrain's fault? Confused...
1. Make an ant/maven/gradle repo, and have the build command run gradle build or something.
2. Create a commandline (open source) tool called "intellibuild" or something, which reads the project files and does whatever the "build" button does.
Unfortunately, they don't do either, so if I don't have a license (or I want to give my code to others who don't use IntelliJ), my J2EE is not buildable.
Re: Visual Studio Code 1.5
#265Earlier quoted context omitted.
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 find relative number very useful to jump lines. Please consider showing current line number for current line. And go ahead with the pull request, many of us need this feature :)
Re: Visual Studio Code 1.5
#266Earlier quoted context omitted.
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 find relative number very useful to jump lines. Please consider showing current line number for current line. And go ahead with the pull request, many of us need this feature :)
Re: Visual Studio Code 1.5
#267Re: Visual Studio Code 1.5
#268I 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!
I had to tweak a minified CSS file for a client project the other day, and granted, VS Code opened the file faster and auto wrapped the output (Atom took a while and showed the file as one long 70000 character single line). However, I noted that VS Code lost all syntax highlighting and displayed everything as a uniform grey text, making it harder to find what I was looking for. Atom retained the CSS syntax highlighti…
Re: Visual Studio Code 1.5
#269I find it interesting that this software isn't designed with Xamarin for all platforms, but instead uses Electron. I mean I get it, the cross platform libraries are better in Electron, but it side steps their current cross platform initiative.
Xamarin doesn't support the platform the editor was originally written for: the web.