Live data from Hacker News

Visual Studio Code 1.5

code.visualstudio.com

211–220 of 270 posts

Re: Visual Studio Code 1.5

#211

Earlier quoted context omitted.

It's a common fallacy to associate quality with price. Generally yes, but not always. Sublime Text certainly isn't 70 dollars better than Atom or VS Code.

For me, it is. Some of the main points that makes it worth money to me are the plugin ecosystem is huge, the editor is fast, its layout management (panes in columns/rows) is incredible, and it was the first editor I had that gave me multi-cursors. I like where VS Code is going and I try to use it when I can, but most of the keybindings and shortcuts I have memorized are for Sublime and IntelliJ based IDEs.

The only thing you listed that sublime uniquely offers is that it was your first and you prefer their key bindings.

Re: Visual Studio Code 1.5

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

WebStorm is very heavy, and its TypeScript support has some issues that were deal breakers for me (last time I tried).

Re: Visual Studio Code 1.5

#213
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?

The debugging experience is vastly superior in VS Code, not to mention the pain of setting it up in vim in the first place.

Re: Visual Studio Code 1.5

#214
Don't use WebStorm!! I installed this piece of garbage last week and it sucks. It is VERY VERY SLOW, has non-standard GUI from Java which has a very bad usability etc. Visual Studio Code is BILLIONS times better and does not cost anything.

Re: Visual Studio Code 1.5

#215
post #24

I really liked Visual Studio Code, but I couldn't really use it without a Vim plugin. So over the last few months I've been working on this one: https://marketplace.visualstudio.com/items?itemName=vscodevi... I think it's gotten a lot better, and if lack of vim keybindings was something that was holding you back from trying VSC, I highly encourage you to try it again!

There are currently three or four different VIM plugins for VSCode and each of them has its issues. After switching a couple of times I'm currently sticking with your vscodevim but I still often run into situations where muscle memory does one thing and vscode does something unexpected.

Still, keep up the good work! ;)

Re: Visual Studio Code 1.5

#216

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

I tried to get C++ working in vscode but ran into trouble getting it to debug with gdb. I was looking for a smooth "hit f5 to compile and run (with breakpoints)" experience like I am used to with VS, but unfortunately there are no tutorials I could find on making that happen. The C++ extension is available, but I can't figure out what exactly it does or how to use it. It suffers from that common problem where they gi…

This may be due to a bug I've filed a few days ago: https://github.com/Microsoft/vscode-cpptools/issues/191#issu... Unfortunately, it seems that the fix hasn't been landed on this release yet.

Re: Visual Studio Code 1.5

#217
post #187

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

Surprised?? With $120+ per year subscription I am surprised people use it.

120 is for businesses. For individual developers its way cheaper: € 59.00 /1st year, € 47.00 /2nd year, € 35.00 /3rd yr onwards. And you can cancel your subscription if you are OK with 1 year old version that you will fallback to.

Re: Visual Studio Code 1.5

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

It is not a strange logic and I am not talking only about quality.

I am talking about IT being one of the few professions in 2016, with individuals that expect to earn money while using tools produced with the effort of others for free (beer), while not giving anything back (not even bug reports, unless their own customers press them against the wall).

So the question isn't about the quality, rather how many Emacs and vi users would have actually payed for them, if they were only available as commercial software?

Re: Visual Studio Code 1.5

#219

Earlier quoted context omitted.

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

It's a common fallacy to associate quality with price. Generally yes, but not always. Sublime Text certainly isn't 70 dollars better than Atom or VS Code.

I wasn't only associating quality with price, but also pointing out that many of the 2016's Emacs and vi users would not use them if they were only available as commercial software.

Regardless of their quality, because the actual IT generation wants to earn money with tools they got for free (beer), while other professions people do pay for their tools.

Re: Visual Studio Code 1.5

#220
post #75

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.

Emacs definitely would be abandoned if not for the GPL. What software developer wants to spend their time in an environment they don't control?!
Post reply on HN