To VSCode’s credit, it aids discovery with tags, filters and sorting. This is a drawback of the “small core” philosophy of VSCode (this reminds me of the Node.js ecosystem). But there are many Git-related extensions for VSCode. GitLens seems to solve this problem (and others). After searching in vain, I realize that there is no built-in support for Git history, and I’m going to need to grab an extension for this. Which changesets did Git pull? I want to look at the history. I think it worked? It said “sync.” What’s a “sync”? To pull, I found a little “refresh” button in my status bar, and clicked it. Happily, VSCode understands this is, in fact, a working copy. But I know origin has changes I need to pull. OK, so I want to edit Mocha’s CHANGELOG.md. It’s difficult to discover what a particular keystroke does at any given time, but also supports conditionals, for a nearly absurd level of control. Key bindings are at once more powerful and complex than WebStorm.
RUN NPM INSTALL WEBSTORM INSTALL
RUN NPM INSTALL WEBSTORM CODE
How smart is it about types and code completion?.
What’s the story on inline errors or warnings?.How does the VCS (Git) integration differ?.What’s debugging look like? How’s the source map support?.What’s the analog of a “Run Configuration?”.Does it support my key bindings, or will I need to relearn everything?.I’ll answer some questions for myself - and, with luck, maybe I can save the JetBrains-faithful some time and energy. Something’s up, and I’m going to get to the bottom of it.
I’ve been a faithful user since P圜harm’s release, seven years ago.Īs of late, if I’m watching a presentation, and someone is writing code in an editor, that editor is almost always VSCode.