Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Visual Studio Code 1.5

code.visualstudio.com

Post reply on HN
Print view View original

91–100 of 270 posts

Re: Visual Studio Code 1.5

#91

Post by alangpierce »

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

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

WebStorm and PyCharm are both (more or less) repackaged versions of IntelliJ with specific plugins. WebStorm is cheaper and just includes the JavaScript support (and other related languages/tools) and PyCharm includes both JavaScript and Python support. So everything in WebStorm is also in PyCharm.

Re: Visual Studio Code 1.5

#92

Post by kozikow »

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

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.

> On this day and age many don't want to pay for tools.

Main part of pycharm is free and open source: https://blog.jetbrains.com/pycharm/2013/10/pycharm-3-0-commu... .

> Sometimes I wonder if Emacs and Vi would be so appreciated if they were commercial as well, without any FOSS version available.

One reason for multitude of emacs extensions is the open source nature. Average IntelliJ user is less likely to write extension than emacs user.

Re: Visual Studio Code 1.5

#93

Post by markcerqueira »

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

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.

> On this day and age many don't want to pay for tools.

Strange logic: if everyone followed that train of thought, we'd all settle for whatever quality tools are available so long as the price is $0. I'd much rather pay for a valuable tool than use a subpar free tool.

Re: Visual Studio Code 1.5

#95

Post by AdamTReineke »

hexis wrote: post #4
out_of_protocol wrote: post #2

Anti-dupe rules are too tight - redirected me to 1.4 discussion (opened a while ago) due to non-unique url

This looks like a reasonable and unique URL for this story - https://code.visualstudio.com/updates/v1_5

@dang (or mods) - Could the URL for the story be updated to this one?

Re: Visual Studio Code 1.5

#96

Post by nikmobi »

Hydraulix989 wrote: post #94

Anybody know how well VS Code works for C++? I really don't like how limited Sublime's linting/static analysis options are.

I've used it a lot for C with great success, although that's not C++.

Give it a shot with the cpptools (I think that's what it's called), as well as the clang extension (which improved the experience by an order of magnitude).

Re: Visual Studio Code 1.5

#98

Post by zerr »

carussell wrote: post #30

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?

Re: Visual Studio Code 1.5

#100

Post by mirekrusin »

markcerqueira wrote: post #93
pjmlp wrote: post #75

Earlier quoted context omitted.

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.

> On this day and age many don't want to pay for tools. Strange logic: if everyone followed that train of thought, we'd all settle for whatever quality tools are available so long as the price is $0. I'd much rather pay for a valuable tool than use a subpar free tool.

That's you. What about the other 7bn people?
Post reply on HN