Live data from Hacker News

Visual Studio Code 1.5

code.visualstudio.com

161–170 of 270 posts

Re: Visual Studio Code 1.5

#161

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

VSCode is open source software. WebStorm isn't. I love JetBrains IDEs but I sure as hell prefer using tools that I can fix or modify myself.

Jet-brains products have a gigantic plugin ecosystem that allows you to add whatever functionality you want..

Re: Visual Studio Code 1.5

#162
post #113

Earlier quoted context omitted.

React may not have "native" support for TypeScript, but in combination with TypeScript using React is so much more fun, if only for the fact that your props can actually be typed and checked at compile time.

The standard recommendation seems to be to use PropTypes. And also in general, to use Babel with React programs. Would be interested to hear experiences of using Typescript with React.

In my opinion React support is progressing quickly but is not fully there yet (definitely more documentation is needed), so for the JSX part the pain is greater than the gain (especially given PropType checking already in React).

As an example, to see what I mean, try to figure out how to write a properly typed Higher Order Component function. Last time I looked at it, this had no direct mention in documentation and only workarounds on StackOverflow.

Re: Visual Studio Code 1.5

#163
post #98

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…

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?

Re: Visual Studio Code 1.5

#164

Opening a newly cloned Chromium repository in ~3s is very impressive to be honest.

I was about to try one of these fancy new browser based editors again, but now I'm confused. Shouldn't opening a directory be O(1)? I just opened the chromium trunk in sublime and it took 0.2 seconds, regardless of whether it was currently running or not. Why would one ever use a text editor that has perceptible latency when doing everyday tasks? 3 seconds isn't even latency, it's a freeze tbh.

I feel we are comparing apple to oranges here: sublime (a text editor) will simply list files & directories in the top level folder when you add a folder to the projects while an IDE (thinking mostly of Eclipse here, but I assume other IDEs aren't that different) will parse every single file to build ASTs, symbol lookup tables and all these things that you either love or cannot stand.

Re: Visual Studio Code 1.5

#165
I am worried about a lot of common functionality in VSCode/Atom, from keyboard bindings to support for more languages, being implemented by 3rd party plugins. They are updated independently, without verification, and have full code execution and network access (and things like independent telemetry).

Am I alone in this? Are there security features that I'm missing to guarantee that my code editor isn't leaking information in 20 different directions?

Re: Visual Studio Code 1.5

#166
post #135

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...

Do I need to do anything to be upgraded to magic python? Thanks!

No, it's on by default in v1.5.

Re: Visual Studio Code 1.5

#168

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

Paying for good tools supports developers who make good tools. I've tried VS Code, but prefer WebStorm.

I pay for a IntelliJ Ultimate license. I am so happy about it. It supports all I want. PHP? Java? Python? Ruby? all you want baby. Consistent UI across all your environment. Solid. Pretty fast. Good Vim plugin. I have absolutely 0 complains. An essential asset.

Re: Visual Studio Code 1.5

#169

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?

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

Re: Visual Studio Code 1.5

#170
post #98

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?

To be honest, to setup vim to provide the features VS Code provides out of the box takes a long time and dedication.

Can't you store your dotfiles on GitHub and just clone them whenever you need your env?

note, I don't do this - I use vanilla vsc for my text editor. I've just seen many who do.

Post reply on HN