Number one drawback of VSCode, for me, is poor vim keybindings, especially visual mode. If that was fixed I'd use it extensively.
Visual Studio Code 1.4
51–60 of 155 posts
Re: Visual Studio Code 1.4
#52I'm not particular about what editor you choose. I've been looking for a good JS IDE. Webstorm is of course the only real player in this space (with an amazing IDE) but it's pricey. I've been watching VSCode with great interest. However, every time I try the editor it's a huge letdown. Buggy, crashy, shitty and weird interface (they have completely made up their own tabbing/splitting paradigm for example, which is bu…
Visual Studio 2015 is the only real player. Have you tried it? I've compared it to every other IDE and nothing comes close. Of course, you need to add quite a few extensions (addons) to make it really nice but other than that, it's got the best autocomplete and the best debugger outside of Chrome Dev Tools. Add the Node.js Tools for VS and the Tools for Apache Cordova extensions (including the kick-ass VS emulator fo…
I've extensively used WebStorm, VS2015, and VS Code for writing JavaScript and TypeScript (both server-side and client-side). VS2015 was the worst of the three. When it worked properly, it was pretty good, but it was incredibly bloated and buggy. It installs GBs of extras onto your machine that you have to painstakingly remove and hope they don't mess anything up. I dealt with a bug that required me to remove some packages and not others. It was a nightmare.
WebStorm is the best, but it's absolutely loaded with features that most people won't use. VS Code supports most of these same features, but they must be implemented manually via config files and scripts. A lot of people will prefer the latter approach because it leads to a leaner starting configuration.
I found the debuggers of all three to be fairly similar, although VS Code's was very slightly less usable.
Edit: To clarify, I used VS Code and VS 2015 at the same time. After getting frustrated with both, I switched to WebStorm and haven't looked back. Every time I think up a "nice to have" feature, I find out that it already exists and is configurable via GUI.
Re: Visual Studio Code 1.4
#53Whenever I try a new text editor, I run into a problem: I absolutely love the feature where it auto-completes based on other words in open windows (or other files in the open project). But there's no official term for this so I can never tell if a text editor has it. Years ago this used to be called "hippie expand", but I can't figure out a more modern name that is used. Does anyone know what Visual Studio Code calls…
Emacs has dabbrev-completion and dabbrev-expand which, I guess, shows its age...
Re: Visual Studio Code 1.4
#54Whenever I try a new text editor, I run into a problem: I absolutely love the feature where it auto-completes based on other words in open windows (or other files in the open project). But there's no official term for this so I can never tell if a text editor has it. Years ago this used to be called "hippie expand", but I can't figure out a more modern name that is used. Does anyone know what Visual Studio Code calls…
You mean you have a text editor that knows what words are on the page in a CHROME tab (for example) Or you mean, that if you've got 2 text files open as tabs in the same VSCODE window typing in 1 tab will auto-complete with words from the 2nd tab? Where have you seen this feature as it sounds AMAZING!
I mean the latter (other open windows in the text editor). TextMate and Sublime both operate this way, as opposed to IntelliSense style auto-complete where it only operates off of symbol definitions (class names, function names, properties and variables, etc). Which makes sense, because TextMate and Sublime don't really "understand" your code like Visual Studio historically does.
Re: Visual Studio Code 1.4
#55Whenever I try a new text editor, I run into a problem: I absolutely love the feature where it auto-completes based on other words in open windows (or other files in the open project). But there's no official term for this so I can never tell if a text editor has it. Years ago this used to be called "hippie expand", but I can't figure out a more modern name that is used. Does anyone know what Visual Studio Code calls…
I don't know what it's called specifically in context of other open Windows, but I'm guessing the functionality could be described as a feature of "IntelliSense" (but I think IntelliSense is Microsoft's name for it).
I wasn't clear about this, but in my experience with Visual Studio back in the day, IntelliSense only operates off of defined symbols (function names, class names, variables, etc). Whereas text editors such as TextMate and Sublime don't seem to "understand" the code as much, so instead they just autocomplete based on all word they find in the open project or Windows. But I actually prefer this more loosy-goosy style of autocomplete, so was just wondering if this new Visual Studio works that way (since it seems to be geared more towards dynamic languages such as javascript than VS was in the past).
Re: Visual Studio Code 1.4
#56Whenever I try a new text editor, I run into a problem: I absolutely love the feature where it auto-completes based on other words in open windows (or other files in the open project). But there's no official term for this so I can never tell if a text editor has it. Years ago this used to be called "hippie expand", but I can't figure out a more modern name that is used. Does anyone know what Visual Studio Code calls…
You mean [autocomplete]( https://en.wikipedia.org/wiki/Autocomplete )?
Yes, but there are two different kinds of autocomplete -- MS's "IntelliSense" style which actually understands your class/function/variable definitions and only gives you options it thinks are legit, versus more loosey-goosey style where the text editor just uses all words it finds in the open project or windows (regardless of whether or not they make sense in the context of the programming language).
Historically, Visual Studio has only done the stricter "IntelliSense" style, but I am wondering if this new version handles the looser cases like TextMate and Sublime do.
Re: Visual Studio Code 1.4
#57Number one drawback of VSCode, for me, is poor vim keybindings, especially visual mode. If that was fixed I'd use it extensively.
Came here to find if it had Vim bindings.. I guess I'll wait to use it :/
Re: Visual Studio Code 1.4
#58I 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.
Those were not invented by Sublime. Lots of older editors have those things, including TextMate and even GNU Emacs and XEmacs. XEmacs had a package manager since the early 1990s.
What Sublime has going for it versus these other editors is ease of use and a much better looking UI. But VS Code has that too, and it's free.
Re: Visual Studio Code 1.4
#59Earlier quoted context omitted.
I love the git integration so much that when I'm preparing to commit on a visual studio (proper) project I'll type `CODE .` in powershell or the package manager console to inspect and edit my code before pushing.
Agreed, I kind of wish that MS could come up with a way to get rebase/squash and pull --rebase working in the editor, having a 3-way merge in VS Code would be awesome... unfortunately it doesn't work well as a system editor choice for git cli. Been very happy with VS Code, though I wish I could revert to pre-tabs file behavior, I'd like the space back... it took getting used to, but the list switcher was a better UX…
> I wish I could revert to pre-tabs file behavior
Adding the following to your User Settings should get you pretty close:
{
"workbench.editor.showTabs": false,
"workbench.editor.enablePreview": false,
"workbench.editor.enablePreviewFromQuickOpen": false,
// ...
}Re: Visual Studio Code 1.4
#60I'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…
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.
I'm curious, what's the thought behind having an official company-wide text editor? The companies I've worked for usually take the route of "leave their choice in tools up to them", which I appreciate.