Visual Studio Code 1.5 • Hacker News Board

Re: Visual Studio Code 1.5

#81

Post by Noseshine » Thu, Sep 08, 2016, 9:24 PM UTC

szines wrote: post #55

bdcravens wrote: post #35

Earlier quoted context omitted.

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.

In terms of WebStorm, dont forget to exclude tmp folders and other generated, transpiled content folder to exclude from indexing, otherweise it will be always busy. :)

Which by the way is the very first thing that I found as recommendation for how to configure projects for VSCode when I tried it today, and very explicitly:

See 'Using the "exclude" property' on https://code.visualstudio.com/docs/languages/jsconfig

    > The exclude attribute tells the language service what files are and are not part of your
    > source code. This keeps performance at a high level. If IntelliSense is slow, add folders
    > to your exclude list (VS Code will prompt you to do this if it detects the slow down).

I went back to WebStorm though after checking VSCode out. I'm using "static type checking through IDE an JSDoc" instead of TypeScript or Flow, although I'm always evaluating both. This far I keep watching them, WebStorm alerts me to type mismatches based on all the JSDoc and Google Closure compiler type annotations I have for each and every variable, function and parameter. VSCode supports it a lot less well than WebStorm, which if you use TypeScript won't matter that much to you. I'll probably go with Flow at some point, WebStorm is getting support for it right now, it's in the current EAP (early access program). I think those who use TypeScript may probably be the closest to getting what I would get from WebStorm, although the latter also has very good TypeScript support. What I like about WebStorm is that they react pretty quickly to (good) bug reports, I filed about a hundred and 2/3rd of them have been solved quickly, of the remaining various type inference issues for example for destructured variables or parameters still need fixing, but that's because of my JSDoc reliance which I'm not sure many other people use.

Re: Visual Studio Code 1.5

#82

Post by RedCrowbar » Thu, Sep 08, 2016, 9:27 PM UTC

Worth mentioning that in this release TextMate Python bundle was replaced with MagicPython [1] for much improved Python code tokenization. [2]

[1] https://github.com/MagicStack/MagicPython [2] https://github.com/Microsoft/vscode/commit/f4967722fa02471da...

Re: Visual Studio Code 1.5

#83

Post by oblio » Thu, Sep 08, 2016, 9:28 PM UTC

memonkey wrote: post #79

aviraldg wrote: post #62

Earlier 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!)

Would creating large applications in WebStorm break things if I wanted to use VSCode in the future or alongside?

Webstorm creates a hidden folder for it settings, in the project folder, and that's about it.

Re: Visual Studio Code 1.5

#84

Post by softawre » Thu, Sep 08, 2016, 9:28 PM UTC

aviraldg wrote: post #62

msoad wrote: post #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! :)

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!)

Does WebStorm still maintain their own version of TypeScript language tools? Back in the 1.0 days they did, and it was a mess. Stuff that would work in Visual Studio and with tsc at the command line wouldn't work in WebStorm.

That said, love Jetbrains. Have a Ultimate license for Java.

Re: Visual Studio Code 1.5

#85

Post by sgt » Thu, Sep 08, 2016, 9:29 PM UTC

aviraldg wrote: post #62

msoad wrote: post #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! :)

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!)

I haven't used WebStorm, but if it's as good as PyCharm (also a JetBrains product), then it'll definitely be worth getting.

Re: Visual Studio Code 1.5

#86

Post by sixothree » Thu, Sep 08, 2016, 9:36 PM UTC

duncanawoods wrote: post #67

romanovcode wrote: post #63

Earlier quoted context omitted.

I'm working with C# on Mac with this and it works perfectly fine. Debugger and intellisense is good enough to work with. It will never be as advanced as VS but then again, VS will (probably) never come to Mac.

Can you share your instructions for setting it up please? I found it very unconvincing last time I tried - I had weird errors installing .net Core, weird errors setting up tools in VS code and found no definitive instructions. I expected it to work pretty much out of the box... but no.

I installed .Net Core on a brand new Mac following the (seemingly very simple) instructions on Microsoft's web site and had errors too. Not impressed with that aspect at all.

Not sure if my fixes were correct or if everything was working correctly so I just abandoned .Net Core on the Mac.

Re: Visual Studio Code 1.5

#87

Post by softawre » Thu, Sep 08, 2016, 9:37 PM UTC

duaneb wrote: post #33

Analemma_ wrote: post #29

Earlier quoted context omitted.

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.

VS Code does good renames (across project) in TypeScript, at least.

VS still has a ton more features though.

Re: Visual Studio Code 1.5

#88

Post by squeaky-clean » Thu, Sep 08, 2016, 9:38 PM UTC

memonkey wrote: post #79

aviraldg wrote: post #62

Earlier 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!)

Would creating large applications in WebStorm break things if I wanted to use VSCode in the future or alongside?

You'd be fine. Webstorm will create a .idea directory in your project, which will contain all the Webstorm specific project settings and configuration. But anything else is stored in regular ol' files you could edit with anything. I use Webstorm and my other teammates use VS Code or Sublime.

The only thing that might "break" is if you rely on Webstorm's tools for things like test runners, compiling, minifying and bundling code, etc, instead of learning how to do it on your own. You'd then need to learn how to set it up yourself with the command line tools instead of a nice GUI.

Re: Visual Studio Code 1.5

#89

Post by Nemcue » Thu, Sep 08, 2016, 9:41 PM UTC

I too switched to VSC from Atom recently, mostly due to the TypeScript-support being vastly superior in terms of both stability and speed.

Really, really wish they would focus on providing a proper crashlog. Right now I'm getting intermittent crashes with no way of reproducing it, nor a good way of providing feedback to the team.

Re: Visual Studio Code 1.5

#90

Post by thatswrong0 » Thu, Sep 08, 2016, 9:42 PM UTC

tracker1 wrote: post #43

dotch wrote: post #21

Earlier quoted context omitted.

I had the same complaints and just went with the excellent ESLint plugin with a ES2016/17 friendly config instead of the default vscode linting.

Agreed, it would be nice if the eslint module swallowed javascript linting errors for you... Also, would be cool if it defaulted to using an in-module copy of eslint with the airbnb preset as it's default if no eslint config file is found in the project/workbench.

IMO the Airbnb preset is too extreme / opinionated to use as a default ESLint config. Maybe something a bit more trimmed down would be reasonable.